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

81–90 of 153 posts

Re: Vue 3.2

#81

Post by iKlsR »

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 think you should swap Vue with React in this take, I'd agree with you 110% if you did that. React is the most over engineered tech I've ever worked with and if it weren't for excellent IDE support a la TS etc would be a nightmare to use on a daily basis. Also Vue 3 has great support for TS, 2 not so much. I can't see myself doing any project without Vue, it's literally plug and play and by far easier to grok and use than React.

Re: Vue 3.2

#82

Post by orangepanda »

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?

Beautiful code and abstractions dont mean nothing if you dont ship anything

Re: Vue 3.2

#83

Post by hahamrfunnyguy »

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…

What are you doing that causes you to need several files for a single component? I am working on a multi-page app using the TypeScript class decorators and .vue component files. I turned off most of the optional features (including babel), and it's just a single .vue file most most components. I configured the Webpack and TypeScript settings when I created the project and haven't had to do much since.

I've used Vue on several other projects and have enjoyed using it every time. I like that parts of the Vue framework are optional. Don't want the router or state management? Don't use it. The codebase is well organized, the output files are small and the app is performant.

I don't like all the dev dependencies you need to get going, but I have that same complaint about most other modern front-end frameworks.

Re: Vue 3.2

#84

Post by dsego »

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.

locality of behavior at its best :)

Re: Vue 3.2

#85

Post by preommr »

Rodeoclash wrote: post #41
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 moved to Vue from ~3 years of React. I've now done ~2 years of VueJS while continuing to use React in some side projects. To be quite honest, I'd probably stick with React if given the choice. My takeaway with Vue is it makes a number of choices for you out of the gate w.r.t to things like data store (Vuex) and routing (Vue-router) whereas with React you'd bolt these on yourself (i.e. mobx and found-router). I also…

Funnily enough the reasons you gave are the reasons I like vue and dislike React.

I like de facto solutions instead of half-baked libraries that might have slight incompatability issues.

I also like the freedom and flexibility that vue offers rather than the weird guardrails that come with react.

Re: Vue 3.2

#87

Post by pixelmonkey »

wirthjason wrote: post #51
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’m not a full-time front end developer, so take this with a grain of salt. I write JS frontends for my nights and weekends side projects. I chose Vue over React because it seemed easier to get up to speed. When I was looking to change jobs earlier this year I spoke with a lot of recruiters and they all said companies were looking for React developers, there were zero mentions of Vue. I don’t really regret my choice…

We chose Vue at Parse.ly after spending quite a lot of time building real-world web products in pre-SPA simple Django + jQuery (2012-2015), then Angular 1.x (2015-2020), and then React (a 1 year experiment, 2018-2019).

We switched our main product to Vue last year, and we couldn't be happier. And, we advertise Vue in our job postings. And, we are hiring!

https://www.parse.ly/careers/frontend_engineer

Re: Vue 3.2

#88

Post by jgalt212 »

Riddle me this:

Developers, in general, despise XML. However, React which is the market leader and generally well-liked is littered with JSX/XML.

Re: Vue 3.2

#89

Post by ianhawes »

SergeAx wrote: post #74
pbowyer wrote: post #49

Earlier quoted context omitted.

> 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/ ?

Have you checked Vue-Native? It hasn’t been maintained since October 2020 and IIRC doesn’t work with the latest RN versions.

Re: Vue 3.2

#90

Post by idoubtit »

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?

> Buggy, insecure, etc. Don't even talk about maintainability!

> who cares?

Some people want their whole website to work for all visitors, so they care about bugs. Some people want their website to stay online and not to be misused by spammers and co, even for non-commercial sites, so they care about security. Some people want their website to evolve for years, so they care about maintainability.

Shipping junk code is delivering... Then a few years later, the owner wants to fix the bugs and add features, and they learn that no one wants to do it unless it's a full rewrite of the legacy code. They have to pay twice for the same features.

Post reply on HN