Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Guide to JavaScript Frameworks

javascriptreport.com

Post reply on HN
Print view View original

31–40 of 244 posts

Re: Guide to JavaScript Frameworks

#32

Post by dandersh »

Klathmon wrote: post #15
paul7986 wrote: post #3

Did 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 s…

Yea I'd say the big churn appears to be around tooling and paradigm thinking (state management, functional programming, etc.), the latter of which driven in part by the rapid expansion of the language itself.

Re: Guide to JavaScript Frameworks

#33

Post by lobo_tuerto »

jmschlmrs wrote: post #25
kowdermeister wrote: post #16

Earlier quoted context omitted.

"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" https://vuejs.org/v2/guide/comparison.html

So is it fair to say that Vue is for people that wish Angular had stayed on the V1 path and not diverged to be more like React for V2 onward?

No, I think it would be fairer to say that it's like if AngularJS and React had a child and named it "Vue.js".

Because in the end, Vue.js has stuff in common with React, like the virtual DOM (you don't see this in Angular 2+) and has stuff in common with AngularJS (the good parts).

Check this out: https://vuejs.org/v2/guide/comparison.html

Don't go thinking you are going to read a biased comparison, the Vue.js vs React section has the blessing from a core React contributor (Dan Abramov): https://github.com/vuejs/vuejs.org/issues/364#issuecomment-2...

Re: Guide to JavaScript Frameworks

#36

Post by ourmandave »

Klathmon wrote: post #15
paul7986 wrote: post #3

Did 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 s…

It's not the frameworks, it's the build tool daisy chain with it's countless dependencies.

Re: Guide to JavaScript Frameworks

#37

Post by naiyt »

Klathmon wrote: post #29
g_b wrote: post #19

Earlier quoted context omitted.

> 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 d…

The one thing that Vue does great is exactly what you say you like about React (edit: not to say there aren't other things Vue does great, just that this is one of them). In Vue you have one file that contains the styles, code, and HTML for the component, all in their own HTML tags. That means that there is a "blessed" solution for styling, that I'm afraid React will never have. Between "styled components", CSS-Modul…

styled-components are actually really nice, so I don't think it's fair to say "styling is React's worst part". This seems like a more general criticism of React's agnosticism when it comes to so many things. React falls more heavily on the library spectrum than the framework one. It's rather un-opinionated about a lot of things: styling, state management, routing, code organization, etc. Definitely not something that's unique to styling.

On the one hand this offers a lot of flexibility to do things the way you want, but also makes the learning curve a lot steeper. Honestly I would love for somebody to build a more full fledged framework around React that makes most of the decisions for you. A sort of "good for 90% of use cases" setup. (I guess create-react-app is sort of like that? You still have to make too many decisions, I think.)

Post reply on HN