Backbone.js VS mustache.js

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

The ajax request is made via a call to Backbone.sync() of Backbone.js, which ultimately calls jquery's $.ajax(). I haven't changed anything about how the call is made... just upgraded cordova.

my gf said it was the best. she uses backbone.js she good dev

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.

Templating engine: SSGs rely on templating engines to define the structure of web pages. These engines enable developers to create reusable templates and incorporate dynamic content. Popular templating engines include Liquid, Handlebars, Mustache, EJS, ERB, HAML, and Slim.

I also enjoy simple templating engines. It makes it far easier to reason about a template and mentally step-through it. For existing art, there are:

DustJS which is a "logic-less" template engine (just loops and simple if-statements): https://github.com/linkedin/dustjs

and there is also mustache, which is very similar: https://mustache.github.io/

Personally, I've re-implemented DustJS in rust but its still a very alpha project: https://code.fizz.buzz/talexander/duster

I think the homepage states, "Logic-less templates"

Other popular templating engines include Jade, EJS, and Handlebars. Jade is a high-performance templating engine that is used for server-side rendering. EJS is a lightweight templating engine that is used for client-side and server-side rendering. Handlebars is a templating language that is based on the Mustache template language.

JSX just a templating language in this case, right? No reactivity at all? What's the benefit against using something like https://github.com/janl/mustache.js/ ?

You don't have to even program the replacement part yourself, because there are many libraries made specifically for that. For this example, I'd recommend mustache.

This is one of the least-bad names because it implements a non-Boost standard and it's named after that. I've used mustache in Python so knew immediately it was a templating language.

First, I setup mustache (npm package) as the templating language (the npm package hasn’t been updated in two years, so that’s great). Mustache is really simple, it provides a few helper utilities, like replacing variables, or iterating over data,

Once the array is ready and back in place, we need to display the information from the emails, and for that we can use the template node. This node uses the mustache system, which is a logicless template engine for creating dynamic content. In other words, it generates HTML code by using tags that are replaced by code.