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

101–110 of 202 posts

Re: Vite 3.0

#101

Post by butz »

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.

What technologies are you working with on backend? I'm pondering to abandon frontend too.

Re: Vite 3.0

#102

Post by qbasic_forever »

skybrian wrote: post #25

I tried using ESBuild directly for a small web app and it seems pretty nice. What would using Vite on top of it give me?

A dev server with hot reloading is the big thing vite adds IMHO, at least for your day to day use. It also adds rollup and a more uniform plugin system for your production builds but really the dev server experience is where vite excels.

If you just want esbuild + hot reloading then dev-server-esbuild might be a good option: https://modern-web.dev/docs/dev-server/plugins/esbuild/ But really vite isn't much more complex or opinionated compared to it.

Re: Vite 3.0

#103

Post by _fat_santa »

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".

Re: Vite 3.0

#104

Post by goodoldneon »

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.

I agree that frontend stuff moves too fast in general, but Vite specifically is a good change. Frontend build systems are a mess (and often slow) so I welcome tools that improve the situation

Re: Vite 3.0

#105

Post by pen2l »

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 from every next person!

Angular and Vue were the thing last I was paying attention. Now React is the thing. But not so fast, there's Next.js.

I think I've had enough, I will supplement my Django backend templates with handwritten CSS.

Re: Vite 3.0

#106

Post by yboris »

benmccann wrote: post #91
enw wrote: post #31

> We decided to release a new Vite major at least every year Isn’t this exhausting? Is it impossible to design good contracts without having to break compatibility every year? In most other language ecosystems it would convey incompetence.

Most apps I've seen can upgrade to Vite 3 without any changes. While there are breaking changes, there aren't a lot and they're not very big.

Confirming: just upgraded to Vite 3 with a one line change in package.json - no other changes were needed :)

Re: Vite 3.0

#107

Post by jbverschoor »

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.

It's too much of the same stuff. Similar frameworks, similar tooling. And they all suck.

I think it has to do with frontend means designers/ux, and those people tend to like being in the spotlight and grab fame. Therefore it's logical that they just create / fork something instead of contributing to an existing project.

This results in buggy projects because they try to do everything, and unmaintained after a while. Usually they're also less thought out than with backend projects.

Re: Vite 3.0

#108

Post by skrebbel »

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.

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 wasteful and also no problem at all.

just don't upgrade random tooling all the time and you're good. most widely used JS stuff has an excellent backward compat story. (react itself is amazing in this regard IMO)

a corollary to this is that if you feel fatigued by having to constantly learn and upgrade your tooling, maybe you're just having regular old analysis paralysis and you're blaming the tooling for no good reason. just use the tools you already know and get going! you can build fantastic, modern-feeling software using only tools and knowledge from a decade ago.

Re: Vite 3.0

#109

Post by ThalesX »

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.

I was just telling my friend yesterday that after a decade of full stack I just don't feel that I can do it anymore. Serverless, bundlers, frameworks, CI / CDs, virtual doms, non-virtual doms, semi-virtual doms, JSON responses, HTML responses, SSR, UI / UX... on and on and on. I have to go through documentation for at least 3 of these things and mush my brain until product decides that that feature is not worthwhile because it can't be done in 2 weeks.

Re: Vite 3.0

#110

Post by jbverschoor »

goodoldneon wrote: post #104
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.

I agree that frontend stuff moves too fast in general, but Vite specifically is a good change. Frontend build systems are a mess (and often slow) so I welcome tools that improve the situation

It doesn't move fast. It creates a lot of noise fast. It's like having a chicken running around, but it gets nowhere
Post reply on HN