Vue
Who doesn't know that one guy, shouting Vue mentioned on every occasion he gets because he pretends people care.
I might be one of t...
For further actions, you may consider blocking this person and/or reporting abuse
One thing no one can deny: Vue developers community created so many tools (and patterns) that became cross-technological and ubiquitous. You can use anything else but you cannot deny the extreme usefulness of being aware of what these Vue guys are cooking next 😄
Nice summary of tooling, it is incredible how the Vue community after the Vite development has crossed the borders to influence and power the whole JS community
React is only more popular because it is backed by Facebook, so more people get to know it first. Otherwise you can use JSX in Vue too, while it is much faster. And once they'll finish Vapor mode and rewrite Vite into Rust, it will be even more performant.
Corporate dinosaurs would advocate for Angular due to enforcing more consistency in bigger projects, but this is also rather a matter of coding skills and design approach. There is no reason you shouldn't write clean and maintainable code in Vue.
It is my number one (especially Nuxt) and I doubt I will move to something else anytime soon.
Well, JSX isn't really first party supported and Vite rewrite won't really increase runtime performance, more compile time. That being said, I think even if people don't plan on using vue, vue ecosystem is kind of prototyping a possible future of JS land, and it looks kind of promising
Fair enough, but it still could be a gamechanger, even if it is "just" compile time - dev.to/justinschroeder/rolldown-wh...
Btw. from a dev's perspective fast compile times possibly mean even more than fast runtime. I have to deal with big legacy Java project in my work. It takes up to MINUTES between making a change and seeing it running...
Sure, faster compile times are always great. What I ment is, vite performance is already quite fast, and generally I never felt like it is blocking me from doing stuff by any means. The build is a bit slower, but I generally look up some docs, start prepping a commit etc or write some small documentation for myself or other devs if they use that library, so I tend to not really notice it. Now, if that is 1 min every time I want to run dev build, yeah, would be anoying for sure ^^
It is true that thanks to Vite's HMR in dev mode I don't even experience "slow" builds that much. Changes I make during development are close to instant now.
progressive means reckless.
I never want to try a reckless library.
h3 is just another reckless ugly creation of a node.js web framework.
I only use angular-like library.