I wonder if Cambrian explosion of JS frameworks stops, will there be a small number of "one-size-fits-all", widely used solutions?
Guide to JavaScript Frameworks
11–20 of 244 posts
Re: Guide to JavaScript Frameworks
#12SEO friendly? Server-side rendering support?
Re: Guide to JavaScript Frameworks
#13Reasons why Vue will rock your socks off - Don't need to know jsx! - Sane way of scripting puts the script in an object and each component is html javascript css - Event buses allow sharing of variables between child components without either redux or pushing variables down one child at a time (finally!) - v-for looping is saner than reacts mapping - v-if allows v-if statements without renderIf component or multiple…
> two way data binding
Maybe it's better in Vue than it was in AngularJS, but this seems like a downside to me.
Re: Guide to JavaScript Frameworks
#14Did you learn Jan2018.js yet? If not your behind and your skills are outdated.....
What? You're still using a JS framework in 2018?
If you haven't already switched to WASM you're about as fullstack as one pancake.
Re: Guide to JavaScript Frameworks
#15Did you learn Jan2018.js yet? If not your behind and your skills are outdated.....
I know people love to shit on JS for being blisteringly fast, but does it really apply here?
All 3 of "the big 3" are over 4 years old, making all of them older than windows 10...
And of the notable category:
Aurelia: around 2014
Elm: around 2013
Inferno: around 2015
Polymer: 2014
Preact: 2016
ReasonML: 2016
Svelte: late 2016
So most a few years old. Yes, it's faster than older technology stacks, because the web is still evolving quite quickly, but it's not as blisteringly fast as many make it out to be.
Re: Guide to JavaScript Frameworks
#16Reasons why Vue will rock your socks off - Don't need to know jsx! - Sane way of scripting puts the script in an object and each component is html javascript css - Event buses allow sharing of variables between child components without either redux or pushing variables down one child at a time (finally!) - v-for looping is saner than reacts mapping - v-if allows v-if statements without renderIf component or multiple…
This sounds very much like Angular 1.
"Some of Vue’s syntax will look very similar to AngularJS (e.g. v-if vs ng-if). This is because there were a lot of things that AngularJS got right and these were an inspiration for Vue very early in its development"
Re: Guide to JavaScript Frameworks
#17Reasons why Vue will rock your socks off - Don't need to know jsx! - Sane way of scripting puts the script in an object and each component is html javascript css - Event buses allow sharing of variables between child components without either redux or pushing variables down one child at a time (finally!) - v-for looping is saner than reacts mapping - v-if allows v-if statements without renderIf component or multiple…
> two way data binding Maybe it's better in Vue than it was in AngularJS, but this seems like a downside to me.
v-model is meant for use specifically with tags, so your local component state stays synced with what the user sees. You can use it on components, but you're not meant to. In general, vue encourages you to avoid using two way data binding on custom components unless your component is a souped up input component, like a fancy date picker or something.
Re: Guide to JavaScript Frameworks
#18They should add the licensing risks around react.
Re: Guide to JavaScript Frameworks
#19Reasons why Vue will rock your socks off - Don't need to know jsx! - Sane way of scripting puts the script in an object and each component is html javascript css - Event buses allow sharing of variables between child components without either redux or pushing variables down one child at a time (finally!) - v-for looping is saner than reacts mapping - v-if allows v-if statements without renderIf component or multiple…
> Don't need to know jsx!
You don't need to know jsx for using jsx. You only need to know html. You do need to learn something more with vue, you said so yourself, those v-for, v-if directives.
> each component is html.file, javascript.file, css.file
I prefer to only have one file per component so that I can just "import Component" and use it. With 3 files I need to make sure all 3 of them get loaded. Disclaimer: I do not know how Vue works.
The rest sound interesting.
Re: Guide to JavaScript Frameworks
#20It's lacking the best - Imba. The rest are just funny toys. Sad it's lacking documentation. Hope it will change soon because it kills with performance and developer experience.
Hmm, “lacking documentation” and “great developer experience” seem mutually exclusive to me.