Live data from Hacker News

Guide to JavaScript Frameworks

javascriptreport.com

1–10 of 244 posts

Re: Guide to JavaScript Frameworks

#5
One non-trivial thing my team has experienced using Angular over the past year; the decision to abandon version numbers makes searching for answers or documentation a nightmare. Ironically the company that should understand search the best hobbled the ability for developers to search for answers.

TypeScript is nice. Actually writing code in angular is a fine experience. It’s all the stuff around that which isn’t great. We recently upgraded our app from Angular 4 to 5 without much fuss and that was nice. But the team should really go back to using version numbers. They exist for good reason.

Re: Guide to JavaScript Frameworks

#7
Reasons 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 render statements in react (antipatterns boo!).

- two way data binding with vue-model

- native vuex with an index file that holds state sanely, rather than just having state held in each reducer as done in react

- Great documentation!

- Yay !

Re: Guide to JavaScript Frameworks

#8

It'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.

This is the first I've heard of it. What, in your opinion, makes it so much better from a developer experience perspective?

Re: Guide to JavaScript Frameworks

#10
post #7

Reasons 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.
Post reply on HN