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

101–110 of 216 posts

Re: Vite 8.0 Is Out

#101

Post by this_user »

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.

Re: Vite 8.0 Is Out

#102

Post by _heimdall »

Zopieux wrote: post #100
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!

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.

Re: Vite 8.0 Is Out

#103

Post by user34283 »

CalRobert wrote: post #12
soulchild77 wrote: post #8

Awesome! Too bad Next.js will never profit from these incredible community efforts, because Vercel suffers from NIH.

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?

Instead of going:

Fetch index.html -> Fetch JS bundle -> Evaluate -> Fetch /users/me

You do:

Fetch index.html (your page is rendered at this point) -> rehydrate with client side JS for interactivity in the background

It's a pretty smart solution I think, and many people are still sleeping on the whole SSR topic.

Re: Vite 8.0 Is Out

#104

Post by brookst »

Aldipower wrote: post #96
__alexs wrote: post #60

Earlier quoted context omitted.

JavaScript was not supposed to a lot of things.

Steve Jobs decided differently when he hated on ActionScript. 10 years ago this sentence probably would have start a flame war. ;-)

Jobs’ complaint wasn’t actionscript the language, it was the security and performance nightmare of the Flash runtime.

Though it’s hard to imagine what the web would look like if the language had become the standard. JS is a pain but AS was even less suitable for general purpose compute.

Re: Vite 8.0 Is Out

#105

Post by littlecranky67 »

J_tt wrote: post #88
littlecranky67 wrote: post #67

Earlier quoted context omitted.

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

Astro: https://astro.build/

From my first glance, it is not really. Has its own templating syntax, its own file format etc. With NextJS static export I only have valid react/tsx and would not want to introduce a framework-specific language. Also could not easily find something about the routing

Re: Vite 8.0 Is Out

#106

Post by littlecranky67 »

christophilus wrote: post #71
littlecranky67 wrote: post #67

Earlier quoted context omitted.

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

It depends on your application, but for typical SPAs, there are any number of approaches which are better than next by every metric I (personally) care about.

Care to list those?

Re: Vite 8.0 Is Out

#107

Post by anon7000 »

user34283 wrote: post #103
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?

Instead of going: Fetch index.html -> Fetch JS bundle -> Evaluate -> Fetch /users/me You do: Fetch index.html (your page is rendered at this point) -> rehydrate with client side JS for interactivity in the background It's a pretty smart solution I think, and many people are still sleeping on the whole SSR topic.

It makes sense for sites with a lot of static pages, but you barely need react in that case. NextJS does not perform that well out of the box. I’d argue that a basic SPA with no SSR using something like preact would be a better choice for many building dashboards or applications (not marketing/docs sites). It’s also easier to host & operate and has fewer footguns.

Getting SSR right is tricky and barely even matters for a lot of use cases I’m seeing with Next.

Better server/client integration when it comes to rendering UIs is neat, but there are other technologies that solve for that at a more fundamental level (htmx, phoenix)

Re: Vite 8.0 Is Out

#108

Post by brillout »

Vite+, Void Cloud, Void Framework... an epic battle between Vercel and Void is coming.

The PRC (aka server functions) demo [0] is particularly interesting — end-to-end type safety (from DB to UI) is a major milestone for JavaScript. We've been doing a lot of RPC design work in that space with Telefunc (tRPC alternative) [1] — it's a really hard topic, and we're looking forward to collaborating with the Void team. (Also looking forward to contributing as the creators of Vike [2].)

[0]: https://www.youtube.com/watch?v=BX0Xv73kXNk (around the end of the first talk) [1]: https://telefunc.com (see the last PR) [2]: https://vike.dev

Re: Vite 8.0 Is Out

#109

Post by mexicocitinluez »

vbezhenar wrote: post #53
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…

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.

> It is especially weird because JavaScript was not supposed to be processed at all! This is all wrong if you ask me.

You're not actually suggesting that technology can't evolve are you? Especially one whose original design goals were to process basic forms and are now being used to build full-blown apps?

It's absolutely wild to me that with everything that has happened in the last 2 decades with regard to the web there are still people who refuse to accept that it's changed. We are building far bigger and more complex applications with JavaScript. What would you propose instead?

Re: Vite 8.0 Is Out

#110

Post by wildpeaks »

dminik wrote: post #94
ZiiS wrote: post #77

Earlier quoted context omitted.

Why would I want to strip my types?

Maybe because TypeScript is not valid JavaScript (yet)? If you don't strip types, your code doesn't work.

It depends on the runtime: Node can run Typescript because it automatically strips types (which is so convenient during development).

But in browser, for now only the more limited JSDoc-style types can be shipped as-is indeed.

Post reply on HN