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

Why we chose Vue.js

about.gitlab.com

Post reply on HN
Print view View original

81–90 of 282 posts

Re: Why we chose Vue.js

#81

Post by rakoo »

Yaggo wrote: post #39
kentor wrote: post #32

After using React, I am firmly in the #nevertemplates camp. I don't ever want to learn a template DSL again when I could be using the full power of javascript.

So what is JSX if not DSL? (Yeah, you can use React without JSX, but still.)

JSX is a DSL for creating HTML, a "language" that has very little custom logic. Vue.js and Angular.js are DSL for creating custom logic, which will always pale in comparison of an actual language designed for custom logic like javascript

Re: Why we chose Vue.js

#82

Post by dflock »

tribby wrote: post #76

vue is awesome. I wish there were an equivalent to something like ember-fastboot for out-of-the-box server side rendering, though. (server-side rendering for those who care about progressive enhancement in the browser, not isomorphism).

Vuejs 2.0 does server side rendering, afaik.

Re: Why we chose Vue.js

#83

Post by a-saleh »

Kiro wrote: post #56

Ok, so I've built stuff in Vue.js, React and Angular and I need to understand all the rage. I mean, Vue.js is just like Angular but with less features? I like that it's slimmer, don't get me wrong, but I just don't understand the "woah, Vue.js is the shit!" when we've had Angular for so long. I put this in contrast to React where it's a completely new concept.

It might be that productivity and maintainability of "more polished" and "simpler" beats "new concept".

It beats angular, because it is both more polished and simpler.

It beats React, at least in short term, because it is both simpler and you don't have to learn new concepts.

People betting on react are hoping that after they internalize those new concepts, it would make it simpler/more maintainable for them in the long run.

Re: Why we chose Vue.js

#84

Post by naranha »

pvorb wrote: post #70
megalomanu wrote: post #58

As a primarly backend dev, I'm very comfortable with React and I don't particularly want to switch to Vue.js. React says me : learn the HTML basics and then deal with abstractions (proof: React Native !). Vue.js says me : deal with HTML templates, everytime, everywhere. Although we even end to deal with HTML in React, I think it's easier for a backend dev with no front experience at all to grasp it. I showed React to…

I keep hearing React reminds Java devs of JSF. But I've never heard it as a compliment.

I am a Java developer who used to work with JSF 2 and I enjoyed it a lot. Now I'm writing a Vue2 app and I finally feel like JS frameworks have reached a stage where I'm nearly as productive with them as I was with JSF, while requiring probably just one tenth of the server resources.

JSF basically provides you with a server side component tree.

Re: Why we chose Vue.js

#85

Post by welanes »

memonkey wrote: post #79
Kiro wrote: post #56

Ok, so I've built stuff in Vue.js, React and Angular and I need to understand all the rage. I mean, Vue.js is just like Angular but with less features? I like that it's slimmer, don't get me wrong, but I just don't understand the "woah, Vue.js is the shit!" when we've had Angular for so long. I put this in contrast to React where it's a completely new concept.

Whoa! Thank you for this. I think this is exactly what I am thinking. I have done exactly what you did and I'm trying to figure out what the rage is as well. I want to find a framework that works for me without all the intricacies and nuances of something so complicated... something that gives me the errors that I need to know to debug the issues I'm having.

Personally, it's the lack of pain when getting started.

React has an unfamiliar syntax and the cognitive load to "get it" while not huge, was going to take time.

Angular seemed fine but a little verbose and a new version was coming out that diverged from Angular 1 in a way that caused more than a few headaches, apparently.

With Vue.js I read through the excellently presented guide and started building my app, instantly.

I view building an app (or app based business) as lego. Join all the pieces together and yay, you have a product. Vue's component based approach matches that perfectly.

Then you look at the small number of open issues on Github, the large number of Vue.js components available (https://github.com/vuejs/awesome-vue), the well-thought-out error messages, documentation and chrome dev extension.

That adds up to a refreshingly pain-free dev experience. As I've mentioned here before, it's so simple it feels like cheating.

Re: Why we chose Vue.js

#86

Post by mhd »

Just pick something, internet and build a good structure on top of it. All this jquery-level bikeshedding is nice for your ad widgets and minimalistic web apps, but it won't help me replace proper GUI toolkits. And sadly, that seems to be in demand...

I'll cope with your ill-designed template language (heck, if I can cope with HTML, I can cope with anything) or your JS async abstraction du jour (promises, async await, that * crap), just give me something on the level of Tk or Swing. I feel like all we got in the last decade beyond e.g. Seaside is a bit less flicker and some more useless animations (looking at you, Material Design buttons).

Re: Why we chose Vue.js

#88

Post by vladimir-y »

ggregoire wrote: post #66
kentor wrote: post #32

After using React, I am firmly in the #nevertemplates camp. I don't ever want to learn a template DSL again when I could be using the full power of javascript.

Same here. In my opinion JSX is one of the best thing happened in the front-end world. Let's not forget how horrible Angular templating was: {{::item.name}}

JSX is just a way to render data, so think like it's a templater, you can integrate it with any tool. React istelf is also just an advanced templater actually, it has no built-in data reactivity despite the name. In my opinion React is not needed in general and JSX is a back to the old fashion PHP coding (Facebook returns to its roots).

Re: Why we chose Vue.js

#89

Post by M4v3R »

wasd wrote: post #26

It would nice if they shared the 30 -> 1 line change.

I'm guessing those 30 lines were for manipulating the DOM or getting the data from form elements. In Vue similarly like in Angular you don't need to write code for that, because the data is 2-way bound. You just do something like this.data = ... and you're done.
Post reply on HN