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

161–170 of 282 posts

Re: Why we chose Vue.js

#161

Post by 49531 »

marpstar wrote: post #158
49531 wrote: post #154

I actually interviewed with Jacob Schatz when he was trying to figure out which frontend framework to use for GitLab. I had been working in React for the last year or so which was apparent on my resume. He prefaced our interview with something to the effect of "I know you do a lot of React but we are not going to ever use React at GitLab" It was weird. I tried to ascertain his reasoning and pretty much all I got was…

Is there a name for this "feeling"? I feel this way about a lot of things that get "popular". I feel this way about React, in fact. React is "good" but I don't see it as our end-all be-all front-end savior. Vue.js is a lot more interesting to me because it's not popular...because it's the underdog. This Cracked article gave me a bit of consolation: http://www.cracked.com/blog/6-reasons-it-sucks-to-hate-popul...

Oh I am the same way in a lot of things, maybe that's why I assumed it was what he was doing :P

Maybe it's just harder to choose a popular option without being seen as jumping on the bandwagon.

Re: Why we chose Vue.js

#162

Post by BaconJuice »

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…

any good resources that goes in depth with features and best practices you can share with us? vue2 specifically?

Re: Why we chose Vue.js

#163

Post by BaconJuice »

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…

any good resources that goes in depth with features and best practices you can share with us? vue2 specifically?

Re: Why we chose Vue.js

#164

Post by rorykoehler »

andrewingram wrote: post #132
k__ wrote: post #116

Earlier quoted context omitted.

I read a writing about how SEO isn't an issue with SPAs. (can't find it at the moment) As far as I know, all major search engines are evaluating JavaScript client-side and index the resulting html, only a chinese one had problems with SPAs. There was even a site from Google, where you could enter a URL and see how Google sees the page.

It's still an issue. Let me show you an example. Here's a website that's an SPA https://preactjs.com I don't have an exact page count, but I was able to find 15 pages from browsing around. Here's how many pages various search engines have indexed using the query "site:preactjs.com" Google: 17 Bing: 6 Yahoo: 6 Baidu: 1 One of the Google results is an error page, but it presumably can't be de-indexed automatically due…

Is that not what sitemaps are for?

Re: Why we chose Vue.js

#165

Post by oldmanjay »

mangeletti wrote: post #152
macspoofing wrote: post #144

Earlier quoted context omitted.

>I don't think it is. You probably want to give it a bit more time. It takes 1 or 2 years after a js framework goes mainstream for the disillusionment and disappointment to set in. We are still in the Vue.js honeymoon phase.

This is because it takes about one or two years before all the hordes of idiots to abandon the last ship they sank and come swimming full speed towards a new ship to sink. The unfortunate part is that it's moments like this (when a framework makes it into the spotlight in a big way like this) that those hordes begin their swim. Evan is an excellent developer, and it won't by through his volition that Vue gets ruined.

Could you expand more on how these hordes of idiots sinks framework by using it? I've never come across a theory about this that's quite so tantalizingly bad before and I'd love you to expound further.

Re: Why we chose Vue.js

#167

Post by WA »

Svenskunganka wrote: post #129
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://a…

Yes, I did and I don't like it very much. Docs are partially in Chinese, almost no examples. Compare this to Ionic 2, which is very close to native elements, including animations.

Re: Why we chose Vue.js

#168

Post by linkmotif »

The thing I like about React is that I don't have to think about the DOM. As soon as I see "el: #id" it's basically over for me. I don't want to think about DOM elements, or at least minimize my exposure to them.

And it's not just that I don't like to think about the browser DOM. It's that I don't want my UI coupled to the DOM. Obviously your UI will be coupled to the DOM to some extent, but React minimizes that. What I love about React is not just `react-dom` but also, say, `react-canvas`, or that you can apply the same principles and work with React Native.

But hey, the more software libs to play with and choose from, the merrier! Cheers!

PS. Relay/GraphQL...

Re: Why we chose Vue.js

#169

Post by k__ »

marpstar wrote: post #158
49531 wrote: post #154

I actually interviewed with Jacob Schatz when he was trying to figure out which frontend framework to use for GitLab. I had been working in React for the last year or so which was apparent on my resume. He prefaced our interview with something to the effect of "I know you do a lot of React but we are not going to ever use React at GitLab" It was weird. I tried to ascertain his reasoning and pretty much all I got was…

Is there a name for this "feeling"? I feel this way about a lot of things that get "popular". I feel this way about React, in fact. React is "good" but I don't see it as our end-all be-all front-end savior. Vue.js is a lot more interesting to me because it's not popular...because it's the underdog. This Cracked article gave me a bit of consolation: http://www.cracked.com/blog/6-reasons-it-sucks-to-hate-popul...

> Is there a name for this "feeling"

I think most people who constantly got this feeling simply didn't outgrow puberty. They just HAVE TO use something different.

But it's okay to look into things and check if they fit you, don't just drink the kool aid. The problem is to have this feeling before testing these things.

Re: Why we chose Vue.js

#170

Post by disease »

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.

React with MobX, Vue and Knockout all seem very similar. I am wondering if TypeScript is a first class citizen in either MobX or Vue - in my experience seeing TypeScript everywhere in Angular 2 has been one of that platform's biggest wins.
Post reply on HN