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

21–30 of 244 posts

Re: Guide to JavaScript Frameworks

#21

Post by chuckdries »

_fol8 wrote: 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…

Seconded for Vue, I used it for a contract project for a year and was consistently blown away.

Gitlab sums it up for me "Vue isn't a buzzword, Vue is a workhorse" https://twitter.com/gitlab/status/928675879676497920

Re: Guide to JavaScript Frameworks

#23

Post by Klathmon »

_fol8 wrote: 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…

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 that I was so happy to escape, needing to learn the "template pseudo language" which ties your hands in a way that I haven't found helpful. But this makes Vue no more wrong or worse than someone using tabs instead of spaces is "wrong" or "worse".

But for others, React is a nightmare because of those reasons. A friend of mine greatly dislikes the React paradigm, and was always more productive and wrote better code in a templating style. And I genuinely don't think it has anything to do with productivity or skill. Vue's style might be better at some things, worse at others, React is the same, but in different ways. They are both fantastic frameworks.

Re: Guide to JavaScript Frameworks

#25

Post by jmschlmrs »

kowdermeister wrote: post #16
jmschlmrs wrote: post #10

Earlier quoted context omitted.

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" 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?

Re: Guide to JavaScript Frameworks

#27

Post by madmaniak »

naiyt wrote: post #8
madmaniak wrote: post #6

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?

It has a syntax dedicated to DOM operations. Doesn't change principles from React perspective - it's component based. So what I do for example: I can copy and paste react code, quickly parse it to Imba notation, and the result is 58 of original 198 lines of code. It's clear and nice to read. And outperforms React tens times. How could I not love it? :)

Re: Guide to JavaScript Frameworks

#28

Post by madmaniak »

burlesona wrote: post #20
madmaniak wrote: post #6

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.

Hmm, “lacking documentation” and “great developer experience” seem mutually exclusive to me.

Some people read documentation, some tests (lol) to know what's going on. I read code - and Imba has really nice code to read. Also they are responsive on Gitter. But as I said. It's a pity.

Re: Guide to JavaScript Frameworks

#29

Post by Klathmon »

g_b wrote: post #19
_fol8 wrote: 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…

> 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-Modules, css-in-js, and tons of other options, many in-operable with each other. Styling is React's worse part, and it doesn't look like it's getting any better...

Re: Guide to JavaScript Frameworks

#30

Post by [deleted] »

jmschlmrs wrote: post #10
_fol8 wrote: 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.

[deleted]
Post reply on HN