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

Vite 8.0 Is Out

vite.dev

Post reply on HN
Print view View original

81–90 of 216 posts

Re: Vite 8.0 Is Out

#81

Post by pjmlp »

christophilus wrote: post #78
wiseowise wrote: post #32

Earlier quoted context omitted.

It takes tooling team and discipline to keep compile times at bay when you reach mid size projects with compiled languages (looking at you Java, C++, Rust).

But, it doesn’t need to be so. Go is pretty fast to compile. So is Jai, from what I’ve seen. So was TurboPascal. Rust has a similar problem to the one Vite has been solving- Rust (and most languages) weren’t designed for compilation speed, and it’s hard to retroactively fix that. But, there’s no reason we shouldn’t have a bunch of statically typed, fast-to-compile languages.

I agree with your remark, only that Rust's current problem is tooling, not the language itself.

See OCaml or Haskell, they also have interpreters and REPLs as part of their tooling.

Also there should be no need to always compile crates from scratch when starting a new project.

Which ironically circles back to your remark of having a similar problem.

Re: Vite 8.0 Is Out

#82

Post by 1dom »

ZiiS wrote: post #77
olmo23 wrote: post #62

Earlier quoted context omitted.

If you're already passing over the sources to strip the types, why would you also not do tree-shaking and minifications?

Why would I want to strip my types?

This feels like a ridiculous thread that captures everything wrong with modern Javascript ecosystem.

It's grown into a product of cults and attempted zingers rather than pragmatic or sensible technical discussions about what we should and shouldn't expect to be able to do with an individual programming language.

edit: to clarify, I assume there needs to be a basical level of comprehension of programming languages to debate the nuance of one, and if you can't think of a single reason as to why someone would want types removed, that's a possible indicator you don't have that necessary level yet, and I think the most effective way for you to learn that is to Google it. Sorry for coming across as rude if you genuinely don't know this stuff.

If you already know many reasons as to why types would be removed, then it seems disingenuous to ask that question, other than to make the point that you feel types shouldn't be stripped. If you think that, say it, and explain why you think they shouldn't be stripped.

Re: Vite 8.0 Is Out

#83

Post by wildpeaks »

ZiiS wrote: post #77
olmo23 wrote: post #62

Earlier quoted context omitted.

If you're already passing over the sources to strip the types, why would you also not do tree-shaking and minifications?

Why would I want to strip my types?

Because it's a waste of bandwidth if they're not enforced at runtime, the same reason why minification exists.

Re: Vite 8.0 Is Out

#85

Post by rk06 »

throwaway290 wrote: post #76

Outsider question: why use Rollup when Esbuild exist? Is esbuild not enough for production builds?

it is not. lack of plugin support is sufficient to block adoptions among other things.

Re: Vite 8.0 Is Out

#86

Post by robertlagrant »

drawfloat wrote: post #46
CalRobert wrote: post #12

Earlier quoted context omitted.

Got back in to react after a few years’ hiatus and I struggle to even understand what the point of Next is. Bizarrely the official docs even reference Next. Are people using react for non-SPA’s? Why?

Vercel has slowly taken over Facebook's position as being the employer of the main developers of React. There's a debate to be had over how much they 'control' it or not, but the fact create-next-app is the first recommended option on the official installation page now does show it's had an impact. 5 or so years ago, Next was a pretty solid option to quickly build up a non SPA, when combined with the static export fu…

I'm trying to build a nextjs app and it's quite painful. It seems to be more and more focused on SSR, which I don't care about (looking for a static app that calls separate API endpoints). That would have been fine in the NextJS I remember from a few years ago, where static and SSR seemed equally viable, but I can't be bothered now. I'm going to try Tanstack Start.

Re: Vite 8.0 Is Out

#87

Post by dbbk »

littlecranky67 wrote: post #67
gherkinnn wrote: post #26

Earlier quoted context omitted.

It's the Vercel way to first run broken previews for several years. Next started with Turbopack alpha as a Webpack alternative in Next 13 (October 2022) and finally marked Turbopack as stable and default in Next 16 (October 2025). They also ran sketchy benchmarks against Vite back in 2022 [0]. Next's caching has a terrible history [1], it is demonstrably slow [2] (HN discussion [3]), RSCs had glaring security holes […

Any suggestions to replace NextJS when you only use static export (no SSR)?

Tanstack Start is the gold standard here. It’ll do a static export no problem.

Re: Vite 8.0 Is Out

#88

Post by J_tt »

littlecranky67 wrote: post #67
gherkinnn wrote: post #26

Earlier quoted context omitted.

It's the Vercel way to first run broken previews for several years. Next started with Turbopack alpha as a Webpack alternative in Next 13 (October 2022) and finally marked Turbopack as stable and default in Next 16 (October 2025). They also ran sketchy benchmarks against Vite back in 2022 [0]. Next's caching has a terrible history [1], it is demonstrably slow [2] (HN discussion [3]), RSCs had glaring security holes […

Any suggestions to replace NextJS when you only use static export (no SSR)?

Astro: https://astro.build/

Re: Vite 8.0 Is Out

#89

Post by bengale »

christophilus wrote: post #70
bengale wrote: post #56

Earlier quoted context omitted.

We saw 12m -> 2m on one of our biggest projects. Incredible really.

It blows my mind that there is a 12m build for a JavaScript application. How may lines of code is this app?

Seems to be around 1 million. It's chunky and it's probably not well optimised for the build to be honest, but it was only starting to creep up the priority list as it crossed the 10m mark.

This is also the length on our CI which is running on some POS build machine. Locally it's far faster, but with Vite 8 its crazy fast.

Re: Vite 8.0 Is Out

#90

Post by ZiiS »

wildpeaks wrote: post #83
ZiiS wrote: post #77

Earlier quoted context omitted.

Why would I want to strip my types?

Because it's a waste of bandwidth if they're not enforced at runtime, the same reason why minification exists.

Both not minifying and including unenforced type hints consumes a little bandwidth though this can be largely offset by compression. This is an engineering trade off against the complexity of getting source maps working reliably for debugging and alerting. If I am shipping a video player or an internal company dashboard how much of my time is that bandwidth worth?
Post reply on HN