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

VueJS turns 10 years old

twitter.com

Post reply on HN
Print view View original

51–60 of 97 posts

Re: VueJS turns 10 years old

#51

Post by habosa »

codethief wrote: post #2

I still don't understand why they had to introduce a proprietary file format. It means that, instead of being able to rely on existing tools for type checking & proper IDE support (like React does), you need custom tools for that custom file format. Unfortunately, developing those takes time – apparently more than 10 years: To this day (I set up a new Vue project just a few days ago) there are countless bugs in vue-t…

Does anyone know of a good open source syntax highlighting library for Vue SFC? That’s my biggest issue with the file format (I maintain a code review tool)

Re: VueJS turns 10 years old

#54

Post by mp05 »

impulser_ wrote: post #47
qudat wrote: post #43

Earlier quoted context omitted.

You haven’t described anything different from what the OP is saying: the main dev behind svelte now works for a company that wants you to use SSR for all your projects. That absolutely impacts feature development to favor sveltekit. The same thing is happening with react. The same thing is happening with deno as well: most active dev is with deno deploy. VC has infiltrated open source development and is driving how f…

What feature was added to SvelteKit on the behave of Vercel?

I don't see where the person said that some feature was added to SvelteKit on behalf of Vercel.

Re: VueJS turns 10 years old

#55

Post by demondemidi »

tgsovlerkhgsel wrote: post #5

I started using VueJS when I got thrown off the deprecation treadmill by Angular. Regardless of whether something is a hobby project that you want to only touch a couple times a year or a big project with dozens of developers, having your platform deprecated under your feet and being forced to do migration work sucks. Vue is now on version 3 within 10 years. That means anyone who relied on v1 has had their work churn…

I'm still on Vue2 for my personal projects because the migration path is painful. Someday I'll get to 3!!!

Re: VueJS turns 10 years old

#56

Post by demondemidi »

ipaddr wrote: post #36
PaulRobinson wrote: post #8

Earlier quoted context omitted.

I was around for the first Angular deprecation treadmill, and it was jarring. I was thinking about doing some stuff for a hobby project recently and as a mostly back-end engineer, I am very out of date for most front-end code. I did a scout around, and didn't feel too impressed. Finally last week I was thinking "I wonder what happened to jQuery", and there it was. Just as it ever was. Updated, freshened up, but compl…

jQuery still works great

It certainly does but only for very flat designs. I was in jQuery camp for a solid 15 years (2000~2015) but once you get a taste of reactive design, it physically hurts to go back to jQuery. For me, that is.

Re: VueJS turns 10 years old

#57

Post by Rapzid »

samwillis wrote: post #42

I think it's a shame the reactivity/signals system from Vue 3 wasn't broken out as a separate project under a different name. They had so much success with building Vite as a separate project, and the reactivity system they built for Vue 3 is so good it warrants the same attention. It can, and is, used outside of Vue, see Alpine.js, but it's adoption would be so much greater if it was packaged under its own name. The…

I agree and that's one reason I've stuck with MobX. Works with React, Vue, Solid, and even mixed solutions. Heck, I've bridged it with backbone codebases..

Re: VueJS turns 10 years old

#58

Post by troupo »

mostlylurks wrote: post #12
troupo wrote: post #3

Earlier quoted context omitted.

You need custom tools for React, too. Because JSX is not valid JS. In most (all?) IDEs you can also tell the IDE to treat the file with a certain extension as written in any language

You don't, because JSX is not required for react. This isn't even just a theoretical point, but something I've actually done in the past several times; it's very convenient to just try something out by throwing react into a script tag and then just writing a small prototype or something without utilizing JSX and thus avoiding the need to set up a build system and everything else. I would still use JSX for larger proj…

> You don't, because JSX is not required for react.

And what does this have to do with the fact that the absolute vast majority of react code is written with JSX and that you need special tools in IDEs to deal with React code (because regular JS tools would break)?

Re: VueJS turns 10 years old

#59

Post by whstl »

mushufasa wrote: post #14
cjblomqvist wrote: post #10

Earlier quoted context omitted.

We have a 100kloc codebase and migrated 2->3 + replaced our whole build stack (webpack -> vite) with a few dev days of effort (mostly on SSR stuff). It hasn't (at least not negatively) our general velocity at all. A totally different thing than moving from Angular 1 -> 2 for example.

We're about to need to do the same thing with similarly sized codebase. Would love to hear your story. Did you find any migration tooling to help? Would be happy to DM to chat as well. One of our issues is that we've used some component frameworks that also need to be migrated.

I did it to a similarly sized codebase too. Vue itself was painless.

I also migrated our component framework, from Buefy to Oruga. Some string replacement to change component prefixes, then Typescript to help catch incorrect properties. I might have fixed several bugs in the process thanks to Typescript working better with Oruga. The only real tricky part was converting customized CSS, which was A LOT in our case, but Oruga provides a better way of overriding CSS, so it was worth the time.

Took about 2 days of me doing pure coding with a blocked calendar, plus a third day for testing and code reviews by the rest of the team.

Re: VueJS turns 10 years old

#60

Post by jthemenace »

We have a large legacy PHP code base originally using "xajax" in many places for asynchronous parts of the UI. We've pretty much got somewhat of our own "framework" and any sort of re-write is absolutely out of the question. We have been slowing replacing xajax with VueJS via a script tag and it's been working great for us as a modern / supported alternative to xajax . There are certain VueJS niceties we can't take advantage of because of the script tag approach, but that hasn't been a big deal.
Post reply on HN