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

111–120 of 216 posts

Re: Vite 8.0 Is Out

#111

Post by mexicocitinluez »

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…

> but the fact create-next-app is the first recommended option on the official installation page now does show it's had an impact.

There is a decent bit of history around that page and whether some things should go in a collapsible div and whether that was prioritizing certain frameworks over other ones.

One thing I'm still salty about is that CRA isn't mentioned anywhere (in the entire site). It's like it never existed.

Re: Vite 8.0 Is Out

#112

Post by nobleach »

littlecranky67 wrote: post #105
J_tt wrote: post #88

Earlier quoted context omitted.

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

While Astro does indeed have its own type of components, it also supports React, Solid and a host of others. So transplanting your current tree of components in, adding the React plugin and saying "GO" is likely a fairly straight-forward project. I moved a previous static site into an older verison of Astro with very little trouble.

Re: Vite 8.0 Is Out

#113

Post by itsTyrion »

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…

the vite Homepage lags on both an A55 and s23fe regardless, which bears at least some irony

Re: Vite 8.0 Is Out

#114

Post by emadda »

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 has been very stable for my projects too.

I think it is the only tool in the JS ecosystem that has not broken after a few years.

Re: Vite 8.0 Is Out

#115

Post by user34283 »

anon7000 wrote: post #107
user34283 wrote: post #103

Earlier quoted context omitted.

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 f…

It rather appears to make sense for any site that currently makes additional requests to fetch data as part of the page load.

It is broadly useful and relatively easy to use while still staying within the React framework the developer knows well.

That said, I didn't build more than a demo app with NextJS, so I don't know a lot about possible issues. Just the concept seems to be good.

Re: Vite 8.0 Is Out

#116

Post by azangru »

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.

> 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?

Re: Vite 8.0 Is Out

#118

Post by azangru »

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?

> Are people using react for non-SPA’s?

Imagine a page that loads html during the first load, and then performs client-side routing during subsequent navigations. Is it an SPA? Is it not an SPA?

Re: Vite 8.0 Is Out

#119

Post by christophilus »

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.

This is the way. Trivial to get live reloading working. HMR is overrated. I went with esbuild in my last project, and have no regrets. Also, used my own 100-line end-to-end typed RPC layer with Zod validation doing the heavy lifting. No codegen required for any part of the project other than generating types from Postgres. No regrets there, either. The only thing I would have changed in that project is I would have used Kysely instead of just raw porsager.

Re: Vite 8.0 Is Out

#120

Post by Aldipower »

brookst wrote: post #104
Aldipower wrote: post #96

Earlier quoted context omitted.

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.

And at least the "performance nightmare" is an irony from today's perspective as the Flash player wasn't actually slow at all! It was the incapability of the Safari browser to handle plugins in a good way and on mobile devices. Today's implementations of mobile application, JavaScript heavy applications and websites are much much more performance heavy.

ActionScript3 was a very suitable language.

Post reply on HN