Hacker News Reader

Comment by max0563 | Hacker News Reader

Vue.js is awesome! I am glad to see so many more people adopting it for serious projects.

I work for a networking company in bay area and a pretty complex major dashboard is built entirely with Vue. I have only heard good things about it from the developers.

Which in turn made me use Vuejs for this hackernews search that I have been building (http://searchhn.com/).

The documentation is excellent and Vue is well designed, it took a few hours from scratch to learn and build the demo (PS: Not a web developer)

That's impressive - you have a pretty good sense of design.

Do you also have a lot of data vars like "inputSearch" "inputTypeSelectionCheckbox" ?

Vue is awesome. I belive it will stick around - for one - they have seminars and well attended events. It's not a one-man project anymore.

It has gained big popularity in the PHP/Laravel world.

On the other hand, we have a somewhat large production vue 1.0 app that we just can't justify quickly upgrading to vue 2.x. I hope to get some more LTS version information from Vue team so we don't have to upgrade to Vue 3 in 2018...

Vue is a proof that good stuff doesn't need advertisement.

I've used Vue for a couple projects now and it's my favorite SPA framework by far. But I liked Knockout too, and now that feels abandoned, and I'm afraid Vue will suffer the same fate. Will it really stick around in the face of React, Angular, and Ember? I feel like there is only room for so many frameworks. So I'm a little nervous to recommend Vue for really large projects. Can anyone offer a good reason why I should stop worrying?

Btw one thing I like about Vue is how easy it is to build a traditional server-rendered app but use Vue only on pages that really need it. Not saying you can't do this elsewhere, but with Vue it is so easy!

Well, Vue can use React, can't it? So they kind of co-exist.

It can use JSX.

> Can anyone offer a good reason why I should stop worrying?

There will always be a shiny new tool, no matter which one you choose. Good products can be built in any of them (even Knockout which I loved too). Most of the frontend fatigue is just paradox of choice. For me what works to reduce paradox of choice is knowing that good architecture and clean code is much more important than the selected framework. Most of them have a lot of documentation, examples, so we should focus on creating good products, and again, most of them can be used to created high quality web apps.

Just my intuitive impression: The VueJS community is already so big that I think its reached escape velocity. It's bigger than Knockout ever was. By now, there's enough invested in vue-based apps that if anything were to happen to the core team, multiple parties would come out of the woodwork to keep it going - it's already too valuable to allow it to die.

The main dev for Vue, Evan You, funds development for it through Patreon[1]. Also, it has quite a few sponsors[2].

[1] https://www.patreon.com/evanyou [2] https://vuejs.org/#sponsors

Also a little company called Alibaba uses vue in production.

https://twitter.com/vuejs/status/669141763760766976

I have been required to use Vue.js in a current project (a semi complex app with lots of forms). It's the perfect way for clueless js fanboys to write unmaintainable spaghetti code. It's nothing less than a poorly designed view layer with no kind of architecture or tooling. It's naive and harmful (because of the way it is being marketed). It's a hobby project by someone that think they know what they are doing, but are really just mindlessly copying features that sound cool from real projects without understanding the underlying complexities or real world challanges. I've worked on large code bases on many different projects, both front-end and backend, with many different frameworks and architectures (including most of the popular js frameworks). Vue.js is the single most stupid and pointless "application framework" I have ever used.

Every framework enables spaghetti code, why should Vue be any different? Heck, any beginner programmer is bound to make spaghetti code.

I'm not going to go into details why Vue is awesome (see all the other comments for that.), but I don't see you bringing any valid arguments for your statements. Sounds like a new framework has been pushed down your throat, and that hurts. I get it :)

Vue.js is basically just a js object wrapping a DOM node. It's claiming to be the equivalent to a full fledged MVC framework (or similar). But it only supplies the V and completely ignores the C and M. Leaving it up to you to invent your own framework on top of it. The parts that Vue.js do supply are not well thought out (Vuex is a nightmare). The parts that do work and are nice are simply straight out copied from other frameworks like Angular. When you give an average developer Vue.js as the only tool you end up with the same kind of code you get when trying to write a complex SPA with jquery: a Single-Pile-of-shit-App.

I'm curious about where you saw claims of Vue.js being a fully fledged MVC framework. Asking because I've always thought that Vue did a decent job of being forward about exactly what it is. Just reading the first paragraph of the guide (https://vuejs.org/v2/guide/):

"The core library is focused on the view layer only"

It seems to be pretty clear that it's meant to be a simple, easy to deploy, view layer only. I think it accomplishes that purpose pretty well. There are additional libraries (Vuex, VueRouter) which extend this core library into something coming close to a full MVVM framework, but those libraries are all maintained separately and not part of the core.

I agree. It's just an uninformed comment. Literally "Vue" means "view" in French.

Like just about all UI frameworks, it's up to you to build a framework on top of it. In your case a LOB type framework.

I'm in the process of doing that very thing for Angular.

By itself, Angular has features to help you do things, but it's far from codifying how a LOB application should be built.

It sounds like some jr devs went willy-nilly with vuejs, but they could have done it with React, angular, jquery, etc...

World's leading Clueless JS Fanboi here: I have literally no idea how you justify anything you just said with facts. If your statements actually had any basis in reality, you should do a write up, because I'm sure this information would be useful.

> It's the perfect way for clueless js fanboys to write unmaintainable spaghetti code

So you are saying that Vue.js is good for experienced devs because it's flexible and lightweight, right? Then I agree.

I'm a senior developer and sometimes I write spaghetti code using React/Redux. I always refactor later but the point is that you can replace instances of "Vue.js" in your comment with the name of _any_ framework and it could be true.

What are your favourite libraries/extensions (for want of a better term) to use with it? I'm on my first VueJS 2 project, and found a number which are abandoned...

Vuex (https://github.com/vuejs/vuex) and vue-router (https://github.com/vuejs/vue-router) are nothing flashy, yet really solid. There are tons more in the awesome-vue repo (https://github.com/vuejs/awesome-vue).

Even though Vue has less libraries/extensions than something like React, the core: state management, routing, Vue component spec are quite good.

Vuex is really nice. I had always been afraid of Redux, Mobx and other flux-like implementations, but after porting a project from using internalized state in each component to one store in vuex this weekend, it ended up being refreshingly simple.

Thanks, "nothing flashy, yet really solid" is EXACTLY what I look for in libraries.

I would also encourage _not_ to use anything else beside Vue-Router and Vuex at first. Most Vue components found on Github are just simple wrappers for already existing modules. In my experience, most components look easy at first but end up being a hassle when you try to get it right in the details (looking at pretty much every JS framework Bootstrap wrapper here). Try writing your own directive or component, it's not hard, you'll learn a lot and I think you'll even be faster.

I'd recommend checking out Vue CLI for structured Vue apps (https://github.com/vuejs/vue-cli). There are plenty of tutorials on using vue-router and vuex with it. Addy Osmani mentioned a progressive web app template at Google IO recently (https://github.com/vuejs-templates/pwa) which gives you things like Service Worker etc

Vue has the best implementation of Material Design I've ever seen: https://vuematerial.github.io/#/

Vuetify is also good. https://github.com/vuetifyjs/vuetify

Well, actually the best implementation of Material Design would be callem'all's http://material-ui.com/. Really mature and full-featured.

vuematerial is slightly behind in the no. of components. After some more research I have settled on using http://www.muse-ui.org/#/index. It has full parity with callem'all's component set. In fact, the website is nearly a full clone of that. And the developer is pretty active.

Case in point - There was an issue with the auto-complete. Raised an issue - https://github.com/museui/muse-ui/issues/495. And it got merged pretty quickly.

http://element.eleme.io/#/en-US is a nice UI framework

Seeing so many new cool projects done in Vue makes me wish I used it instead of ng2 for my pet project. Ah well, I'll keep it in mind for the next one

Reply on news.ycombinator.com