4 ms·
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 unmaintai
by niho 9y ago
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.
- jeppebemad 9y agoEvery 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 :)
- niho 9y agoVue.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.
- sizimon 9y agoI'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/ 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.
- juandazapata 9y agoI agree. It's just an uninformed comment. Literally "Vue" means "view" in French.
- IanDrake 9y agoLike 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...
- Can_Not 9y agoWorld'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.
- mastazi 9y ago> 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.
- abustamam 9y agoI'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.