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

121–130 of 216 posts

Re: Vite 8.0 Is Out

#121

Post by MrJohz »

azangru wrote: post #116
vbezhenar wrote: post #53

Earlier quoted context omitted.

It is especially weird because JavaScript was not supposed to be processed at all! This is all wrong if you ask me. Web development should strive to launch unchanged sources in the browser. TypeScript also was specifically designed so engine could strip types and execute result code. These build tools should not exist in the first place.

> TypeScript also was specifically designed so engine could strip types and execute result code. These build tools should not exist in the first place. Was it? Have you forgotten namespaces and enums?

More recently, it's been designed so this is the case. Namespaces, enums, and the property constructor shortcut thing were all added relatively early on, before the philosophy of "just JS + types" had been fully defined.

These days, TypeScript will only add new features if they are either JavaScript features that have reached consensus (stage 3 iirc), or exist at the type system only.

There have been attempts to add type hints directly to JavaScript, so that you really could run something like TypeScript in the browser directly (with the types being automatically stripped out), but this causes a lot of additional parsing complexity and so nothing's really come of it yet. There's also the question of how useful it would even be in the end, given you can get much the same effect by using TypeScript's JSDoc-based annotations instead of `.ts` files, if you really need to be able to run your source code directly.

Re: Vite 8.0 Is Out

#122

Post by echelon »

_heimdall wrote: post #102
Zopieux wrote: post #100

Earlier quoted context omitted.

I wonder what will be the parallel hindsight about waste, but for matrix multiplications, in a few years.

By then I understand that matrix multiplication will have cured cancer and invented unlimited free energy, so no hindsight of waste needed.

Cure cancer? It doesn't have to cure cancer for it to make billions.

All it has to do is put price pressure on your salary. (And it is already doing that.)

Re: Vite 8.0 Is Out

#123

Post by Sammi »

jillesvangurp wrote: post #98
raydenvm wrote: post #80

Yeah, it makes you wonder how much computing power the industry has wasted over the years on tools that nobody questioned because "that's just how long builds take." We planned our work around it, joked about creating breaks, and built entire caching layers to work around it. Kudos to the Vite maintainers!

Build performance has been a pet topic for me for quite some time when I realized I was wasting so much times waiting for stuff to build 14 years ago. The problem is especially endemic in the Java world. But also in the backend world in general. I've seen people do integration tests where 99% of the time is spend creating and recreating the same database over and over again (some shitty ruby project more than a decad…

> I've seen people do integration tests where 99% of the time is spend creating and recreating the same database over and over again (some shitty ruby project more than a decade ago). That took something like 10 minutes.

For anyone that doesn't know: With sqlite you can serialize the db to a buffer and create a "new" db from that buffer with just `new Datebase()`. Just run the migrations once on test initialization, serialize that migrated db and reuse it instantly for each test for amazing test isolation.

Re: Vite 8.0 Is Out

#124

Post by jjice »

karel-3d wrote: post #41

Yesterday I stopped hating AI because it converted an old webpack project with impenetrable plugin settings to a single simple Vite config. I still don't understand how people used to think scripts like this are the proper way to bundle an app. https://github.com/facebook/create-react-app/blob/main/packa... vite is great, is all I am saying

800 lines config to compile code that's later interpreted is wild. I get the general idea behind having a script instead of a static config, so you can do some runtime config (whether or not we should have runtime changes to config is a different conversation), but this is absurd.

I'm a big believer in fully reviewing all LLM generated code, but if I had to generate and review a webpack config like this, my eyes would gloss over...

Re: Vite 8.0 Is Out

#125

Post by chrisweekly »

Awesome news. Amid all the (real and perceived) js ecosystem churn, vite has been consistently excellent for dx and production. The unified rolldown bundler is only going to increase vite's appeal and widen the gap as the fastest, most pragmatic and flexible foundation for ts/js projects. Huge fan, speaking from deep experience (webdev since 1998).

Re: Vite 8.0 Is Out

#127

Post by silverwind »

Aldipower wrote: post #95

As I am interested in long time maintainability (should still work in 10 years) with my projects I am just using esbuild directly. I am not interested in adjusting my projects, just because things changed under the hood in "wrappers" like Vite and I suddenly have a lot of work.

IIRC, esbuild is still lacking code splitting.

Re: Vite 8.0 Is Out

#128

Post by chearon »

Aldipower wrote: post #95

As I am interested in long time maintainability (should still work in 10 years) with my projects I am just using esbuild directly. I am not interested in adjusting my projects, just because things changed under the hood in "wrappers" like Vite and I suddenly have a lot of work.

esbuild still doesn’t support top-level await. And live reloading is way, way slower than HMR.

Re: Vite 8.0 Is Out

#129

Post by [deleted] »

this_user wrote: post #101
homebrewer wrote: post #47

Very pleased to see such performance improvements in the era of Electron shit and general contempt for users' computers. One of the projects I'm working on has been going for many years (since before React hooks were introduced), and I remember building it back in the day with tooling that was considered standard at the time (vanilla react-scripts, assembled around Webpack). It look maybe two minutes on a decent deve…

> Very pleased to see such performance improvements in the era of Electron shit and general contempt for users' computers. Luckily, we have invented a completely new nightmare in the form of trying to graft machine-usable interfaces on top of AI models that were specifically designed to be used by humans.

[deleted]

Re: Vite 8.0 Is Out

#130

Post by c-hendricks »

nebezb wrote: post #18

> Built-in tsconfig paths support A great QoL change. One less place to duplicate (and potentially mistake) a config.

This is great news, but people should also try using regular nodejs import aliases and see if they're viable for their project.
Post reply on HN