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

Vite – Next Generation Front End Tooling

main.vitejs.dev

Post reply on HN
Print view View original

21–30 of 383 posts

Re: Vite – Next Generation Front End Tooling

#21

Post by config_yml »

jbrooksuk wrote: post #14

We (Laravel) have just switched the frontend tooling from Laravel Mix (a webpack wrapper) for Vite. https://laravel.com/docs/9.x/vite#main-content The speed gains are super impressive from Vite.

I think Rails should have done the same, vite_ruby is amazing. Thankfully it's easy enough to replace the current options, which feel a bit half-hearted.

Re: Vite – Next Generation Front End Tooling

#22

Post by steve_taylor »

xisukar wrote: post #8
matchbok wrote: post #2

The constant iteration and revolution of basic front-end web dev makes me happy to be a mobile dev.

You're being downvoted but it's wild how frontend frameworks pop up, take hold, and then quietly disappear with the next iteration of the same thing with different syntactic sugar.

Yeah, it's not like a single web framework has been the most widely used for seven years running. Oh, wait...

Re: Vite – Next Generation Front End Tooling

#23

Post by root_axis »

xisukar wrote: post #8
matchbok wrote: post #2

The constant iteration and revolution of basic front-end web dev makes me happy to be a mobile dev.

You're being downvoted but it's wild how frontend frameworks pop up, take hold, and then quietly disappear with the next iteration of the same thing with different syntactic sugar.

I downvoted it. I did so because, IMO, the comment is superfluous noise seen on every js thread. A tool exists to solve a problem, if you don't understand why it was built or don't like it, that's ok, but the hackneyed complaining about open source software merely existing deserves to be at the bottom of the thread.

Re: Vite – Next Generation Front End Tooling

#25

Post by sampullman »

candiddevmike wrote: post #12

I'm a happy vite user, but it troubles me when I think about how complicated everything it abstracts has become. It uses rollup for some things, esbuild for others, workbox for my service worker... I switched from webpack to it, and while my config is certainly less complex, I at least could tell you what webpack is doing. Vite is magic. Can I just use esbuild yet?

I think Vite is waiting for code splitting and plugin support in esbuild.

It does seem like magic sometimes, but the the code is relatively straightforward. It's not too complicated to dig into to the internals if you're curious about how specific configuration works under the hood. With Webpack I never really felt that way, but maybe it's some kind of subconscious bias from struggling so often with massive configs.

Re: Vite – Next Generation Front End Tooling

#26

Post by mmargerum »

xisukar wrote: post #8
matchbok wrote: post #2

The constant iteration and revolution of basic front-end web dev makes me happy to be a mobile dev.

You're being downvoted but it's wild how frontend frameworks pop up, take hold, and then quietly disappear with the next iteration of the same thing with different syntactic sugar.

Javascript UI frameworks last longer the Microsoft UI frameworks. It's not like a newer framework is just replacing an old one because of hype. React/Vue are massive improvements over Angular 1.

Re: Vite – Next Generation Front End Tooling

#27

Post by DrewADesign »

matchbok wrote: post #2

The constant iteration and revolution of basic front-end web dev makes me happy to be a mobile dev.

I get your frustration: only being partially invested in front-end web dev, the constant churn of what people consider viable stacks, techniques and architectures can be maddening. It can all seem like a race to implement the hottest javascript du jour in some finicky framework or library while sweeping inscrutable, increasingly complex webpack implementation details under the rug... until they pop out, or the rug catches on fire, or the floor gives out, or any other inevitable thing happens that precludes ignoring them.

Maybe plastering a power strip into a wall rather than doing proper electrical work is a better metaphor. Everybody knows it’s a bad idea, but someone made a thing that automatically provisions and deploys new strips, and someone made a thing that plugs stuff in, and someone made a thing that mixes and applies plaster which was replaced by a drywall thing but we still call it plaster, and someone else made a thing that does it in 10 rooms at once…

That said, this seems like a bigger step towards simplifying both the development process AND the toolchain. It only works in newer browsers so it doesn't immediately work for all use cases, but it's good enough for some. We're quickly approaching the point where browser-native implementations of more recent, better designed scripting features are widespread enough to rely on. That should both simplify and stabilize front-end web development for quite some time.

Re: Vite – Next Generation Front End Tooling

#29

Post by fomine3 »

xisukar wrote: post #8
matchbok wrote: post #2

The constant iteration and revolution of basic front-end web dev makes me happy to be a mobile dev.

You're being downvoted but it's wild how frontend frameworks pop up, take hold, and then quietly disappear with the next iteration of the same thing with different syntactic sugar.

React era is long.

Re: Vite – Next Generation Front End Tooling

#30

Post by gedy »

sandreas wrote: post #4

I think sveltekit[1] uses this :-) 1: https://kit.svelte.dev/

It does, but fyi vite cli has built in support for Svelte, and you can bootstrap a project really easily if you don't need all the "stuff" that sveltekit provides:

npm create vite@latest my-app -- --template svelte-ts

Post reply on HN