Which MV* Javascript framework to choose according to the given conditions?

Question

JavaScript

Good afternoon.
Foreword: I
read a comparative review on Habrahabr and other third-party sites, looked at todomvc.com , but because I don’t have experience with JS solutions, so I can’t decide.

Need help choosing a JS framework to write the following single-page application (an exaggerated example to understand the essence):
1. RESTful API
2. There is a calendar on the page, for every day you can create entities (events), which are actually contained in the database, and with which the main work is carried out.
3. You can scroll through the calendar in any direction, create as many entities as you like on any day, and everything should be instantly synchronized with the server.
4. In addition to working with the Calendar and entities by day, other functionality is minimal (settings page and a couple of dialog boxes).

That is, we have 1 table for the necessary entities, let's say Events. And one table Users.

So far I have chosen Backbone.js. Isn't this an overkill?

Another important point: in the examples reviewed, after loading the page, Backbone GET initializes its models with a request. Is it possible to initialize it with an array without an extra request by embedding it (the array) on load in the page code. If yes, is it normal?
Thank you.

Answer 1

Based on personal experience in implementing Rich-frontends, I can say that there are several important points that are often forgotten - in backbone-like frameworks, memory leaks are often observed during intensive content downloads / updates. I've had experience implementing projects where "everything is in one JS and html file" in the literal sense, with real-time content updates via socket.io... and there memory leaks were the main problem.
I tried knockout, ember, meteor, spine, backbone... but Angular showed itself the best in this regard, although the principles and rendering speed in it still leave much to be desired. There are at least 2-3 backbone forks (remakes) in the world that are designed to save their progenitor from leaks.
From history: twitter somehow implemented their entire service in a similar way, after a while they had to break everything paginated to force garbage collection.
Here in the rest of the interfaces, I'm most worried about the lack of normal support for http caching - support for if-modified-since tags, and etags.
From what it is... it's restangular and it's very raw. The module built into the angular resource is still very much cut, and it specifically lacks features, but it should be enough for your tasks.
I'm not sure if angular would be a viable choice for a single-page case, it might be worth looking into spine + handlebars / jade.
Some complain about the high entry threshold for angular, although it seemed to me that everything is quite simple there and the documentation is quite good. It seemed to me even simpler than Backbone. But the taste and color...

Answer 2

-