Yes, it's a lot. But imagine the opposite. Imagine nothing new came out, and everything just stagnated. Evolution, experimentation, testing things out, this is a good thing.
Guide to JavaScript Frameworks
111–120 of 244 posts
Re: Guide to JavaScript Frameworks
#112I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…
This is an opinion, so don't take it as fact, but JS frameworks are a mistake. It's better to take the Unix philosophy and build things up from single components that do their one job well, and focus on standards. So an example would be to use Web Components rather than React. React is amazing but it has a limited lifespan (though that lifespan could be long), whereas Web Components, while not as feature rich, are a…
I don't know... not all web standards worked well in the past: xhtml, appcache, etc. I wouldn't be surprised if web components never got success. Why should anyone use this standard when a library is 10 times better? Being the standard is not enough.
Re: Guide to JavaScript Frameworks
#113Earlier quoted context omitted.
Honestly I don't think Vue is better than React, or React better than Vue. They are just different, and that's where a lot of the arguments come from. For me, Vue is such a monumentally large step backwards. I loved React because there are no templates, there is no 2-way binding, you don't have the vuex style state handling. Using Vue is an exercise in frustration for me, dealing with all of the templating headaches…
To me React is superior for a very simple reason. There is a huge deficit of intermediate-advanced Vue tutorials compared to React. There are like 30 advanced-level tutorials on Egghead on React and like, what 3-4 advanced Vue tutorials (Nuxt, Nuxt and using Angular-like decorators to write proper classes instead of the 'it just works' vanilla boilerplate)? Learning the ropes of Vue is easy. It's a go-to framework of…
Add to that tooling compatibility issues with TypeScript & Vue
Re: Guide to JavaScript Frameworks
#114Earlier quoted context omitted.
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 s…
They appear and disappear as fast as startups and projects which use them:)
Do you have any information or statistics or studies to add, or did you just want to post your quippy oneliner?
Re: Guide to JavaScript Frameworks
#115Earlier quoted context omitted.
I've used Vue for larger project and like it but the things you list are the drawbacks IMO: - Don't need to know jsx! But you need to learn Vue's template DSL. JSX is just HTML and JavaScript. - v-for looping is saner than reacts mapping - v-if allows v-if statements without renderIf component or multiple render statements in react (antipatterns boo!). Strongly disagree! - two way data binding with vue-model I sugges…
JSX is NOT just HTML and JavaScript! If it was just html I could write and not , I could write instead of . It's not even just javascript, or I would be able to write a simple if-else statement. JSX is a DSL, a minimal one, but still. I mean, you could say it's even worse, because those subtle differences can cost you hours of looking for mistakes.
It is Javascript, but JSX brackets only allow an expression within them. Conditionals are statements in JS, so you have to wrap them in an IIFE or a `do`-expression.
Re: Guide to JavaScript Frameworks
#116Earlier quoted context omitted.
This is an opinion, so don't take it as fact, but JS frameworks are a mistake. It's better to take the Unix philosophy and build things up from single components that do their one job well, and focus on standards. So an example would be to use Web Components rather than React. React is amazing but it has a limited lifespan (though that lifespan could be long), whereas Web Components, while not as feature rich, are a…
I don't know... not all web standards worked well in the past: xhtml, appcache, etc. I wouldn't be surprised if web components never got success. Why should anyone use this standard when a library is 10 times better? Being the standard is not enough.
You're just assumming the library is 10x better.
One reason to use web components would be it allows for a much more lightweight abstraction over DOM.
Re: Guide to JavaScript Frameworks
#117The Ultimate Guide to JavaScript Frameworks: Use pure HTML, CSS and JS.
Yeah I used to think that.
If you have any amount of dynamic data with a non-trivial representation, and you don't want to have to go through awful ad-hoc things of "when I update this data structure, tell the stuff on the screen to change" and "when this on-screen value changes, update these parts of the data structure", you eventually end up with an MVC framework: this is not a new idea and JS didn't invent it.
And once you have that, adding a bit of structure to make it nice to build up modular components results in something pretty close to Vue or React.
Re: Guide to JavaScript Frameworks
#118I come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requi…
I could have written this myself. I did a lot of web development before JavaScript exploded and have since done mostly back end work. Every time I hype myself up to learn any of this stuff I feel like I'm chasing my tail.
"Wait, I can't learn this until I understand that, but that requires some knowledge of that other thing which is best understood in the context of..." It's exhausting. I have written code professionally in a dozen languages or more on projects ranging in size and scope, but I have never felt so lost as when trying to learn the labryinth that is the JavaScript ecosystem.
Re: Guide to JavaScript Frameworks
#119What are the "clear best practices" for Angular? I'm just starting in Angular 5 and I'm starting down the ngrx path. From what I can tell there's many different ways to structure the project and ngrx is in version hell - the current docs on master reflect an unreleased version.
Re: Guide to JavaScript Frameworks
#120Whats the right choice for building a repacement for an existing app that has survived for 15 years and you want the replacement to last at least another 10? Whats the long term hedge?
If you think Facebook will still be there in 10 years, then you can safely pick React.
> If you think Facebook will still be there in 10 years, then you can safely pick React.
At the same time, you could've made that same argument at some point with Google and AngularJS, Dart, Polymer, etc.
Not necessarily a safe bet.