riot VS Backbone.js

how about getting a hold of your sanity and allowing yourself a few hours to learn https://riot.js.org/ - almost no learning curve, only pure awesomeness. even if you won't use it in the enterprise (because policies, bla bla), it is still worth knowing things can be done differently - in a good way.

Riot.js prides itself as a light and simple UI library that helps developers hit the ground running when creating elegant UIs for their applications.

Thanks! Glad you like it. I'm the original author of Riot (https://riot.js.org/) so that's the style of frontend development I'm most comfortable with. We're using our own flavour of the library, which has the original super-mimimalistic feel on it.

Got it thanks for the context.

I've read the web app and it seems to me it is just https://backbonejs.org/ re-written in Typescript and allows JSX.

I'm very certain Typescript and JSX will have improved the DX for Backbone like apps, but it doesn't address all of the other issues that teams had with Backbone.

e.g. Cyclical event propagation, state stored in the DOM (i.e. appendChild is error prone in large code bases), etc.

What we see, a decade ago, are that many of the "popular" libraries, frameworks, and methods, not surprisingly, have gone by the wayside, a lot that have remained in current code as difficult-to-removemodernize legacy cruft (Bower, Gulp, Grunt, Backbone, Angular 1, ...), and then we have the small minority that are still here. Some that remain have had their utility lessened/questioned by platform and language improvements (jQuery, lodash, ...), but very, very few exist that are the same now as they were then. Another fun historical reference: issue #118 of "JavaScript Weekly" (February 22, 2013) includes a first link out to asm.js.

Backbone.js gives structure to web applications by providing models with key-value binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing API over a RESTful JSON interface. site Backbone.js *Backbone.js gives structure to web applications by providing models with key-value binding and custom events…*backbonejs.org

Backbone.js

A lot of SPA frameworks and libraries also were developed. We can find out some of its on the internet. They are AngularJs, Reactjs, BackboneJs, DurandalJs,.. and a lot of third party components to make the Javascript coding more easy like RequireJs, Amplifyjs, BreezeJs...

As the internet became faster, and more reliable, and as browsers unified into “evergreen” releases, developers accepted JSON to be the only shape of data needed to travel on wires. A few years back I posted a question of which was a better framework: serving fully processed HTML scripts over Ajax, or only JSON that would be populated on client-side. See, back then, populating JSON was hand crafted, before Knockout, before Backbone, and few other players I don’t recall. The thing you could use back then was Mustache-like, which -by the way- still is a favorite of mine when venturing outside of SPA zone.

In the early 2010s — while Jekyll was being reinvented — web browsers were becoming ever more capable, spurring a proliferation of companies developing single-page applications. However, building single-page web applications required a level of shared data consistency that the most popular JavaScript framework at the time, JQuery, was not equipped to handle. We saw a number of frameworks tackle this problem, including Backbone, Ember, Knockout, and most popular, AngularJs. These frameworks provided a structure for creating large applications.

Backbone - A JavaScript library with a RESTful JSON interface and is based on the MVC application design paradigm.