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

121–130 of 282 posts

Re: Why we chose Vue.js

#121

Post by LaurentVB »

iotscale wrote: post #103
anonyfox wrote: post #34

As someone who went through the complete frontend hype-trains (jquery, backbone, angular, ember, react, all in production): Vue.js 2.0 with single file components is exactly what everyone looks for desperately. - performance: faster than react now - learning curve: a few hours from scratch - getting started: cli-tool for initial scaffold & configuration - components: simple .vue files with a , and . Super easy to get…

I started reading through the docs and found it very similar to Knockout.js. Is here anyone who used both to tell the advantages of Vue? FYI, I'm thinking about dropping Knockout because some performance problems I'm having with a very specific use-case.

Exactly my thought when I tried Vue.js: on the surface, it's knockout with some react-inspired additions that make it faster. I loved being able to pick up Vue.js and make something that just worked in 30 minutes.

Re: Why we chose Vue.js

#122

Post by SonicSoul »

gregmac wrote: post #11

I do very little web these days, mostly working on backend data processing, network I/O and distributed comms. A bit over a year ago, I wanted a real-time web UI to visualize some of the data I had on server-side, which I was trying to do using SignalR. I went back through some of the popular frameworks, with a pretty simple mindset of "Can I read the 'getting started', and get something basic working in about 15 min…

hmm I used signalR with angular 1.x and can't speak for your 15 min requirement but I definitely didn't have any need for proxies or model mapping. I suppose if you're using knockout you'd need that (at least call a utility function to translate plain objects into KO objects) but did you find that with Angular?

Re: Why we chose Vue.js

#123

Post by iotscale »

vladimir-y wrote: post #88
ggregoire wrote: post #66

Earlier quoted context omitted.

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).

React is not a templater, it's a differ. The only similarity between PHP and React is that you can have tags in ("around" in PHP's case) your code.

Edit: After reading my comment again, I feel I must mention; even that similarity is not coming from React directly. It's JSX. Although they go like fish & chips together (Not a great analogy but I guess I'm hungry).

Re: Why we chose Vue.js

#124

Post by nkozyra »

syaz1 wrote: post #80
ggregoire wrote: post #66

Earlier quoted context omitted.

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}}

Wow, that looks really messy for what is essentially printing items in collection...

I believe that will always be the case when you have to embed logic into a relatively rigid markup language.

Syntactically, JSX feels more native, but both are addressing the same problem.

Re: Why we chose Vue.js

#125

Post by haalcion3 »

I'd like to discuss the following comparison in: https://vuejs.org/guide/comparison.html#Angular-2

> Vue 2.0 seems to be ahead of Angular 2 according to this 3rd party benchmark. ( http://stefankrause.net/js-frameworks-benchmark4/webdriver-t... )

The latest benchmark provided is actually:

https://rawgit.com/krausest/js-framework-benchmark/master/we...

But, Angular 2 is v2.1.1 now, released 2016-10-20. Someone should update: https://github.com/krausest/js-framework-benchmark

However, as they say, "In terms of performance, both frameworks are exceptionally fast and there isn’t enough data from real world use cases to make a verdict."

And Angular 2 Hello World is easier than they make it seem in the comparison:

> starts out with an app that uses ES2015 JavaScript, NPM with 18 dependencies, 4 files, and over 3,000 words to explain it all - just to say Hello World.

It's just the following with a lot of documentation that could be simplified:

  mkdir angular-quickstart
  (add package.json)
  npm install
  mkdir app
  (add app.component.js)
  (add app/app.module.js)
  (add app/main.js)
  cd ..
  (add index.html)
  (add styles.css - optional step)
  npm start
Also, it makes the case that Angular2 is "enterprise" because many use TypeScript with it. But, TypeScript is optional in both Vue and Angular2, so people could just as easily make the argument that Vue is "enterprise" because it supports TypeScript.

Finally, it's true that Google uses/develops Angular2, so that's some significant backing. If you want to see who's using Vue:

https://github.com/vuejs/awesome-vue#projects-using-vuejs

That doesn't mean anything on its own, though. It could be just fine to use and expect to continue to be hyped.

Re: Why we chose Vue.js

#127

Post by WA »

I tried Vue.js a few months ago and liked it a lot. But now, I need to rewrite my apps and I decided to go the Cordova road with Ionic 2, because Ionic 2 is, imho, unparalleled in its quality.

Ionic 2 uses Angular 2 and I wished there was some Ionic 2 + Vue.js bindings. However, after working with it for a bit, I found that Angular 2 is actually quite simple with the benefit of using TypeScript out of the box.

Before you dismiss Angular 2, give it a try. It's fundamentally different from Angular 1: easier to learn, less complex, faster results.

Re: Why we chose Vue.js

#128

Post by sotojuan »

shriek wrote: post #105
octref wrote: post #42

To me Vue is a great tool for side projects. In React I found myself struggling to figure out what libs to use and keep myself up to date with them. I also hated configuring webpack. With Vue, I have officially supported libraries like vuex and vue-router which work great with Vue out of the box. vue-cli also allows me to scaffold projects with these libraries very easily. But the thing I like most about Vue is it al…

Wait, Vue doesn't need to be transpiled to JS like JSX? I'm equally hating configuring webpack. It's lack of documentation isn't helping either.

Why aren't you using create-react-app?

Re: Why we chose Vue.js

#129

Post by Svenskunganka »

WA wrote: post #127

I tried Vue.js a few months ago and liked it a lot. But now, I need to rewrite my apps and I decided to go the Cordova road with Ionic 2, because Ionic 2 is, imho, unparalleled in its quality. Ionic 2 uses Angular 2 and I wished there was some Ionic 2 + Vue.js bindings. However, after working with it for a bit, I found that Angular 2 is actually quite simple with the benefit of using TypeScript out of the box. Before…

Have you looked at Weex[1]? It's what Ionic is to Angular, the only difference is that Weex and Vue has an official collaboration and Weex has been embraced by Vue's developers - something that Ionic hasn't yet been by the Angular team as far as I'm aware.

Note though that the collaboration is still very young between these two, but I believe we'll see some great things in 2017 from this collaboration!

[1]: https://alibaba.github.io/weex/

Re: Why we chose Vue.js

#130

Post by daenney »

ta834939874 wrote: post #21
greyskull wrote: post #12

There's something that irks me about incorporating logic into templates. UI development is hard enough without having to bounce between js and templates to figure out how a component is actually going to behave. I haven't used Vue or React, so this is all just my gut speaking, but at least with React all the logic is there in front of you. In my mind, if there's a loop or a conditional or whatever piece of logic that…

Vue single file components behave very similar to React. The main reason I chose React over Vue is that I found React components were much easier to compose than Vue. This mainly came from them using handlebars, a very suitable library for when Vue was first implemented. From what I understand, soon you'll be able to use JSX in Vue components - which would negate this advantage. I would certainly consider Vue again f…

It's already possible to use JSX with Vue components, since the 2.0 release.
Post reply on HN