Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vue 3.2

blog.vuejs.org

Post reply on HN
Print view View original

71–80 of 153 posts

Re: Vue 3.2

#71

Post by IceDane »

Vue is hands down the worst frontend framework I've had the displeasure of working with. The authors are trying to hard to write something "different" that in the end they've only managed to create a bunch of incidental complexity that you constantly have to deal with because of their design decisions. And then they keep trying to "fix" these problems by adding new features and more complexity.

Everything in Vue is more complicated. They went with this whole template language which is just a mess and has extremely poor tooling support. Everything is more complicated and harder to reason about. You literally need(ed) several files to write a single component which could be a couple of lines of JSX in React. Since the tooling support is so poor and it is so over-engineered, it is extremely difficult and bothersome to get it fully typed.

I'm just really glad that I don't have to work with it on a daily basis.

Re: Vue 3.2

#72

Post by jgrpf »

5350-uiop-1130 wrote: post #37

Anyone moved from React to Vue. I've been reading the Vue docs and I like some things about it but the compositional model seems a bit more confusing compared to React. Also, I think I do prefer working with JSX versus using html templates. I prefer that close coupling of JS logic and JSX presentation. The most appealing thing about Vue is that it seems to be more of a framework, maybe somewhere in the middle between…

I switched some years ago and never looked back. What I really like about Vue is that I can use it with a build system or just add it with a script tag for a bit of progressive enhancement over a form. I think it is simpler and decreased my bug count. I'm mainly a backend developer though.

Re: Vue 3.2

#73

Post by jgrpf »

Bellamy wrote: post #54
5350-uiop-1130 wrote: post #37

Anyone moved from React to Vue. I've been reading the Vue docs and I like some things about it but the compositional model seems a bit more confusing compared to React. Also, I think I do prefer working with JSX versus using html templates. I prefer that close coupling of JS logic and JSX presentation. The most appealing thing about Vue is that it seems to be more of a framework, maybe somewhere in the middle between…

What about security and upgrading? I've heard there is some pain upgrading Vue, but there is definitely pain when upgrading React. At the moment one of our previous React projects "npm install" gives 4000 security issues.

React might have stabilized in the meantime but a couple of years ago the upgrade pain definitely was there.

Re: Vue 3.2

#74

Post by SergeAx »

pbowyer wrote: post #49
5350-uiop-1130 wrote: post #37

Anyone moved from React to Vue. I've been reading the Vue docs and I like some things about it but the compositional model seems a bit more confusing compared to React. Also, I think I do prefer working with JSX versus using html templates. I prefer that close coupling of JS logic and JSX presentation. The most appealing thing about Vue is that it seems to be more of a framework, maybe somewhere in the middle between…

> Anyone moved from React to Vue I'm considering a move in the opposite direction for a few reasons: 1. React Native. I can build mobile apps using Vue via Ionic Framework / Cordova / Capacitor but that ecosystem is a nightmare (esp the Cordova/Capacitor split). React Native has more extensions available and the camera related ones are considerably more featureful. 2. Libraries/widgets. Vue has widget libraries avail…

1. Have you checked https://vue-native.io/ ?

Re: Vue 3.2

#75

Post by Tade0 »

chillydawg wrote: post #68
coolgoose wrote: post #57

I really wonder if all developers that really like jsx + inline grapql aren't old school php4 developers that were writing php logic and sql queries in the view itself.

those were the days! I was really productive in that mode, although the quality of output was 1/10 at best. Buggy, insecure, etc. Don't even talk about maintainability! But, but! You got it done real fast and most of the time for some random website that doesnt handle money, who cares?

I got back to doing this for a brief moment a few years ago.

The effect was just brutally hideous, but it worked.

Makes one wonder if all this sophisticated tooling we're using currently is actually worth it.

Re: Vue 3.2

#76

Post by MatekCopatek »

IceDane wrote: post #71

Vue is hands down the worst frontend framework I've had the displeasure of working with. The authors are trying to hard to write something "different" that in the end they've only managed to create a bunch of incidental complexity that you constantly have to deal with because of their design decisions. And then they keep trying to "fix" these problems by adding new features and more complexity. Everything in Vue is m…

That's really interesting, I've worked with Vue since before 1.0, used it for various things (complex conventional SPAs, enhancing legacy server-rendered apps, even an IPTV GUI) and was always really satisfied.

Can you give a few examples of things that bug you?

Re: Vue 3.2

#77

Post by ebr4him »

AstralStorm wrote: post #62
Tajnymag wrote: post #59

Earlier quoted context omitted.

Wow. That's exactly what I thought Vuex would look like after after the Vue 3 release. Definitely going to use it for my future project.

Just know what you're getting into, this is a new rather unknown framework with much fewer users and resources than Vue with VueX.

Read the docs, its from a Vue core team member and based on a future version of Vuex so you can easily migrate.

Re: Vue 3.2

#78

Post by tnjm »

IceDane wrote: post #71

Vue is hands down the worst frontend framework I've had the displeasure of working with. The authors are trying to hard to write something "different" that in the end they've only managed to create a bunch of incidental complexity that you constantly have to deal with because of their design decisions. And then they keep trying to "fix" these problems by adding new features and more complexity. Everything in Vue is m…

That's interesting -- my experience has been 180° away. I agree that recent features have added complexity and made the barriers for newcomers a little higher, though.

At its core, however, everything just 'clicked', the templating works beautifully, and single-file-components are superb. I'll write React and Ember when necessary, but coming back to Vue is always a welcome relief.

I've lost count of the number of times I decided to start off writing what felt 'right' intuitively, and found things just worked first time. In that sense at least, there are echoes of Rails for me.

Re: Vue 3.2

#79

Post by acallaghan »

IceDane wrote: post #71

Vue is hands down the worst frontend framework I've had the displeasure of working with. The authors are trying to hard to write something "different" that in the end they've only managed to create a bunch of incidental complexity that you constantly have to deal with because of their design decisions. And then they keep trying to "fix" these problems by adding new features and more complexity. Everything in Vue is m…

I've had the exact opposite experience to this, completely and utterly the other way around with React being over engineered and complex, with Vue being the tidier and faster to deal with. I get that React is the industry 'standard', but having worked with both for a while now, Vue is to me hands down better.

Also with Vue, you have community driven direction, rather than FB. This is a big positive for me.

Re: Vue 3.2

#80

Post by MatekCopatek »

MentallyRetired wrote: post #27
Crazyontap wrote: post #14

We've been pretty happy with Vue 2.6 and haven't had the motivation to take the leap. I did try it and even though it's advertised as somewhat backward compatible it did break lots of things, which was totally expected and it's a major release. Also we couldn't figure out a lot of things, like how can I access the $children like before, why does everything show Object proxy in console, etc. Posting on SO and forums a…

I personally love Vue 2.6. I'm not a huge fan of the composable API.

In case you're not aware - the Composition API is entirely optional and will most likely remain that way. It brings more flexibility but also adds complexity and makes components less readable.
Post reply on HN