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

Vite 3.0

vitejs.dev

Post reply on HN
Print view View original

121–130 of 202 posts

Re: Vite 3.0

#121

Post by FinalBriefing »

_fat_santa wrote: post #103
capableweb wrote: post #3

The landing page of Vite claims "Next Generation Frontend Tooling" but then go on to describe features that already have been existing for a good while (multiple years). What exactly is the "next generation" part here? The composition? That's also not new, so I think I'm either missing something very obvious, or they need to do a better job explaining how Vite is actually different.

What I think they are referring to is the bundler is built with Go/Rust rather than JS (like Webpack). The difference in speed between Webpack and any bundler built in Rust/Go (SWC, Vite, Parcel, etc) is that the latter are like 10X faster, not "this is building faster" but "how the hell did it build this quick". That difference in speed is what I think of when they refer to "next generation".

Also, it does away with legacy JS imports. It doesn't use or support CommonJS without a plugin.

Re: Vite 3.0

#122

Post by skrebbel »

ThalesX wrote: post #111
skrebbel wrote: post #108

Earlier quoted context omitted.

Our frontend is mostly class-based react components compiled with webpack 4 and babel 6 (for context: those are old versions). and guess what? it all just works. new 3rd party components also just work. adding modern hooks-based functional components just works. and everything that worked 5 years ago still just works. I think the JS our tooling emits is backward compatible with IE9 and up, which is ridiculous and was…

> just don't upgrade random tooling all the time and you're good. Good luck with that in the NPM ecosystem

I just told you we successfully do exactly this.

Note, it was different ~5 years ago. When we wanted to upgrade from react 15 to 16 for better runtime speed, we had to upgrade babel first and that required a webpack upgrade iirc. It was a mess. But the ecosystem has matured a lot since then and we haven't done major setup changes since. It just works.

Re: Vite 3.0

#124

Post by wishinghand »

s1k3s wrote: post #94

I can't keep up with this stuff anymore. As a former "full stack" dev, I just quit the frontend part altogether and I'm now just focusing on the backend. It's just too much and changing too fast.

Can't keep up with what? There's a few Javascript frameworks, and React is the lion's share of job postings. There's a few build tools but most everyone uses Webpack. The unit testing tools work on frontend and backend, and mostly seem to center around Mocha or Jest.

There was a short lived explosion of frontend frameworks that grognards drag up like it's a relevant problem, but serving up HTML from a server side route has always been an option.

Re: Vite 3.0

#126

Post by elforce002 »

s1k3s wrote: post #94

I can't keep up with this stuff anymore. As a former "full stack" dev, I just quit the frontend part altogether and I'm now just focusing on the backend. It's just too much and changing too fast.

3yrs going fullstack and I feel your pain.

I went with Nextjs with all its bells and whistles and expressjs (99% of cases is enough). Now I'm currently moving to MLE projects at work.

I only pay attention to new tech only if here's a huge demand (ie. Plenty of Jobs and good $$$). Only then I start learning it.

Nextjs/React won the frontend battle (atm). It's almost impossible to keep up + being specialist. Heck, it's equally difficult to be a generalist with new things coming up every 3/6 months.

Re: Vite 3.0

#127

Post by kriberg »

pen2l wrote: post #105
s1k3s wrote: post #94

I can't keep up with this stuff anymore. As a former "full stack" dev, I just quit the frontend part altogether and I'm now just focusing on the backend. It's just too much and changing too fast.

Hear, hear. I'd been away from the scene and recently returned, backend historically was the greater challenge for me since I thought I had an eye for design and could whip up basic things using the more fundamental building blocks. I come back, and I can't tell one thing from the other. SPA, or server-side rendering? Will SPA get me dinged because crawlers can't deal with them? I don't know, I get a different answer…

You can check out htmxhtmx and alpinejs, those complement django quite nicely and you dont have to go down the javascript rabithole to get some dynamicism.

Re: Vite 3.0

#128

Post by Kiro »

I feel all these snarky comments about complexity in front-end development is really misplaced in a thread about Vite, a tool that actually tries to fix that.

Re: Vite 3.0

#129

Post by ramesh31 »

__ryan__ wrote: post #84
ramesh31 wrote: post #50

Earlier quoted context omitted.

>Vite is framework agnostic. Framework specific work is spearheaded by framework specific community or core authors in some cases (solid, astro) This is like saying NPM is language agnostic. Sure, technically it is. But we all know what it was built for and what the community is geared toward.

…Vue in this case?

Yes.

Re: Vite 3.0

#130

Post by rk06 »

s1k3s wrote: post #94

I can't keep up with this stuff anymore. As a former "full stack" dev, I just quit the frontend part altogether and I'm now just focusing on the backend. It's just too much and changing too fast.

You don't need to keep up with this stuff. Just need to be aware that these tech exists and evaluate them when need arises.

In many companies, you won't be tinkering with vite at all. The build person will do that, you will be reaping the benefits of it only.

Post reply on HN