Why we chose Vue.js • Hacker News Board

Re: Why we chose Vue.js

#221

Post by cageface » Fri, Oct 21, 2016, 4:22 PM UTC

mambodog wrote: post #214

askmike wrote: post #196

Earlier quoted context omitted.

I disagree as soon as you write more than a single nested child/parent component, that requires a different way of thinking (should I use state or props?). And that you can't "just uses react". You kind of have to use redux (or similar) as well as a bunch of other stuff.

People keep saying you 'have to use redux' but I think that's hugely misleading to a large section of potential React users who don't need the highly complex state management that redux facilitates, and could get by just fine with setState+props. I'd hope that people who are being exposed to this idea at least also get the chance to read 'You Might Not Need Redux': https://medium.com/@dan_abramov/you-might-not-need-r…

Amen to that. Seems like everybody is cargo culting Redux but really you can get pretty far with just React plus some wrapper components to hold state.

Re: Why we chose Vue.js

#222

Post by agentgt » Fri, Oct 21, 2016, 4:23 PM UTC

A long time ago (7-10 years ago) Web 2.0 was the craze. It was the beginning of making interactive web applications.

There were few major players that were even backed by companies: Dojo, Prototype, GWT, (and like 4 more that I can't remember).

These libraries were complicated and were generally component based with their own flair of inheritance. You could not iteratively enhance your existing web 1.0 app. You had to throw it out and start over again (the markup and all).

Then along came jQuery and I remember distinctly saying to myself this is the library because I can progressively/iteratively add it to our existing crap (circa 2006-10). I still pat myself on the back on being right about that library being successful (I actually forced a previous employer to use jQuery over GWT and Dojo).

Progressive enhancement is a great marketing point so maybe Vue.js will pull a jQuery :)

Personally I want Elm to take off but it doesn't really reuse existing knowledge.

Re: Why we chose Vue.js

#223

Post by wishinghand » Fri, Oct 21, 2016, 4:25 PM UTC

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…

I've been waiting on the Quasar Framework (http://quasar-framework.org/) to mature as it's basically Ionic for Vue.

Re: Why we chose Vue.js

#224

Post by [deleted] » Fri, Oct 21, 2016, 4:35 PM UTC

agentgt wrote: post #222

A long time ago (7-10 years ago) Web 2.0 was the craze. It was the beginning of making interactive web applications. There were few major players that were even backed by companies: Dojo, Prototype, GWT, (and like 4 more that I can't remember). These libraries were complicated and were generally component based with their own flair of inheritance. You could not iteratively enhance your existing web 1.0 app. You had t…

[deleted]

Re: Why we chose Vue.js

#225

Post by holon » Fri, Oct 21, 2016, 4:46 PM UTC

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.

I've used both Knockout and Vue for frontends that needed to render reasonably large amounts of disparate elements with near real-time updates, so I think I can answer this. Knockout is nice but feels closer to jQuery in that it requires a lot more discipline on the behalf of the developer to organise and maintain code. Things like ObservableArrays means dealing with another layer of abstraction; the wonderful thing with Vue is that it's just native JS objects all the way down. It also has a better structured child/parent component model with event flow, not to mention being much faster for rendering. I would also recommend Vue over Knockout.

Re: Why we chose Vue.js

#226

Post by Touche » Fri, Oct 21, 2016, 4:50 PM UTC

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.

No, what happens is a new framework comes out that fixes the complexity problems of the previous popular framework, but ignores why that complexity existed in the first place.

Once the new framework gains popularity the limitations caused by ignoring complexity start to surface and so the framework has to add features to handle them, creating complexity of its own.

Then the cycle repeats itself.

Re: Why we chose Vue.js

#227

Post by hesarenu » Fri, Oct 21, 2016, 4:55 PM UTC

askmike wrote: post #196

hesarenu wrote: post #54

Earlier quoted context omitted.

React is very simple. You need to understand only its basic life cycle. Rest is just JavaScript.

I disagree as soon as you write more than a single nested child/parent component, that requires a different way of thinking (should I use state or props?). And that you can't "just uses react". You kind of have to use redux (or similar) as well as a bunch of other stuff.

You don't need to use redux. But it's very useful to manage state. I went from using simple components to flux to redux all in same project. For me State management is a very part of client ui.

Re: Why we chose Vue.js

#228

Post by szx » Fri, Oct 21, 2016, 5:02 PM UTC

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

Contrarian? Skeptic?

Re: Why we chose Vue.js

#229

Post by subbu » Fri, Oct 21, 2016, 5:02 PM UTC

babyrainbow wrote: post #100

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…

> it's a seriously underrated benefit. It is not without a cost, the cost being an lack of standard ways to accomplish things. For long running projects where devs may come and go, having a standard way to do things is an incredible advantage, and will result in a much more consistent code base. For real world front end project, this is a much more important concern, imho, than ease of picking up. For your particular…

Long running projects in JavaScript may not be that long really. If you leave any codebase for a couple years, things would have changed so drastically, new devs may not even recognize the code. An year old JS project may be using React, a 2-year-old project could be using Angular, a 4-year old project might be using Backbone, a 6-year-old could have $("#el").bind() all over while 8 year-old project could have been in Prototype.js.

Re: Why we chose Vue.js

#230

Post by jeppebemad » Fri, Oct 21, 2016, 5:03 PM UTC

We _just_ started using React, primarily for it's server side rendering support in .NET with Reactjs.net. Works really well and the React mindset feels great.

Coming from Angular 1 though, Vue has a lot of appeal. Is there any support for SSR in .Net, or anything in the pipeline? I've not been able to find anything.