3 ms·
They're not a standard though. Everything's only a year old and gets replaced next year. Where's Backbone gone? Or Knockout? Or Handlebars? Is it NPM, Bower or
by mattmanser 11y ago
They're not a standard though. Everything's only a year old and gets replaced next year.
Where's Backbone gone? Or Knockout? Or Handlebars? Is it NPM, Bower or a mix of the two? Or etc. etc. Are you writing coffeescript still, why not typescript? Did you make an app in Durandal? Haha! Time for Aurelia!
Angular 1, one of the longer lived projects, is literally just being turned into a non-standard after a whole lifetime of about that of the family hamster.
So they're not standards, they're all today's hotness that won't be used on tomorrows projects.
It takes a couple of years for coding standards in new languages and libraries to even evolve, no-one knows how to use it properly to begin with and everyone makes a mess in a different way as they deal with the quirks and build non-trivial projects, but eventually a consensus is born.
In JS frameworks, just as that is happening, the whole thing is abandoned rapidly for the new hotness.
- nilliams 11y agoJust want to be the counterpoint here. I've been building stuff at my last 2 jobs in Backbone (plus good OOP) for the last 5 years, and am only now considering a move to React or Vue, Vue being the conservative choice I may well go with. Not everyone jumps on the new frameworks just because. The JS community is massive and very good at publicising their tools, so there are lots of (very visible) options, and it can give the impression that everyone is constantly switching tools, but that doesn't mean you actually have to.
- maaaats 11y agoThat doesn't invalidate the point, though. I'd rather maintain an old Backbone app, where I can read tutorials and search SO for answer, than some home-made framework.