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

151–160 of 282 posts

Re: Why we chose Vue.js

#151

Post by randomnumber314 »

kentor wrote: post #48
Yaggo wrote: post #39

Earlier quoted context omitted.

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

You can think of it as sugar for `React.createElement()`, and some other stuff (like spread) but that's it. It's really easy to translate into javascript in your head. Why is this good? 1. Let's say I want to stick a debugger in my template or render function. How would you do it in Vue? Angular? I don't know, gotta look it up, not even sure if possible. How would you do it in React? I don't have to look anything up,…

>How would you do it in Vue?

     {{ data | json }}
will give you formatted json output of the data object (i.e. state/props) In reality you can put anything that's in the Vue object's scope between curly braces, pipe it through the json filter.

>immutable list in Vue

    {{item}}

Re: Why we chose Vue.js

#152

Post by mangeletti »

macspoofing wrote: post #144
Svenskunganka wrote: post #134

Earlier quoted context omitted.

I don't think it is. I've been closely keeping an eye on Vue since its first release, and it has really matured quite well and steadily since then. I like to reference Vue with the Crystal[1] programming language, which has looked closely on mainstream programming languages and adopted the good parts of them, like Go's concurrency model, Node's asynchronous I/O, Ruby's clean & straight-forward syntax and object-orien…

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

Re: Why we chose Vue.js

#153

Post by lucaspottersky »

skc wrote: post #93

I hate web dev. Yet I'm loving the experience of working with VueJS. I think alot of people feel this way. The library is just that simple and straightforward.

Today's "simple" is tomorrow's "complex".

1. someone trims your product down and ship it as "simpler than X" 2. people asks for more and more 3. now you have a complex product 4. repeat

Re: Why we chose Vue.js

#154

Post by 49531 »

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 "just because it's popular doesn't mean it's good".

Regardless I think GitLab is an awesome company, I just got the feeling Jacob wanted to use Vue.js because it wasn't the most popular choice. ¯\_(ツ)_/¯

Re: Why we chose Vue.js

#155

Post by jakecodes »

antarrah wrote: post #41

> He pointed out that when a major software company releases a their secret sauce, there is going to be hype. Devs think to themselves,'That company writes JS differently than me, and they are prominent and successful. Is their way of writing JS better than mine? And therefore must I adopt it?' Ahaha. No, believe me I'll not. That's ironic coming from GitLab. I mean I love that company but their front-end sucks big t…

We are constantly working on improving our frontend, and have big plans ahead, so I'd be really interested in hearing what "sucks big time" so we can fix it.

Re: Why we chose Vue.js

#156

Post by masklinn »

randomnumber314 wrote: post #151
kentor wrote: post #48

Earlier quoted context omitted.

You can think of it as sugar for `React.createElement()`, and some other stuff (like spread) but that's it. It's really easy to translate into javascript in your head. Why is this good? 1. Let's say I want to stick a debugger in my template or render function. How would you do it in Vue? Angular? I don't know, gotta look it up, not even sure if possible. How would you do it in React? I don't have to look anything up,…

>How would you do it in Vue? {{ data | json }} will give you formatted json output of the data object (i.e. state/props) In reality you can put anything that's in the Vue object's scope between curly braces, pipe it through the json filter. >immutable list in Vue {{item}}

> {{ data | json }}

So neither debugger support nor printf-debugging, you just have to hope you'll be dumping garbage in a place where it can be seen and doesn't break the page entirely?

> {{item}}

Ignoring that vue changed the name of the directive a while ago[0] that doesn't even remotely work, according to its documentation v-for (née v-repeat) works on native arrays, it's not going to work in any sensible manner on immutable.js structures.

[0] https://github.com/vuejs/vue/issues/1200

Re: Why we chose Vue.js

#157

Post by adamnemecek »

These discussions almost never mention cycle.js. I haven't done front end in a couple of years but whenever I read something from the author of the framework, I'm pretty impressed and the choices they made seem very promising.

Re: Why we chose Vue.js

#158

Post by marpstar »

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

Re: Why we chose Vue.js

#159

Post by SparkyMcUnicorn »

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.

https://vuejs.org/guide/comparison.html#Knockout

I've used Knockout before and it's really slow. I also find Vue to be less complex overall in comparison to Knockout.

Re: Why we chose Vue.js

#160

Post by sotojuan »

macspoofing wrote: post #144
Svenskunganka wrote: post #134

Earlier quoted context omitted.

I don't think it is. I've been closely keeping an eye on Vue since its first release, and it has really matured quite well and steadily since then. I like to reference Vue with the Crystal[1] programming language, which has looked closely on mainstream programming languages and adopted the good parts of them, like Go's concurrency model, Node's asynchronous I/O, Ruby's clean & straight-forward syntax and object-orien…

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

Keep in mind Vue isn't backed by Facebook or Google, so it'll take longer for hype to set in as Evan You can't market it heavily or organize large conferences by himself.
Post reply on HN