Another rewrite in Rust. What about finally stop using node.js for server side development?
[flagged]
Vite 8.0 Is Out
31–40 of 216 posts
Re: Vite 8.0 Is Out
#32Earlier quoted context omitted.
This is for tooling. Node.js has been extraordinarily useful for building build tools. We're outgrowing it's capacity and rightfully moving to a compiled language. Also faster tooling is essential for establishing a high quality feedback loop for AI agents
Why go halfway, embrace compiled languages in the backend. Fast all the way down, especially when coupled with REPL tooling.
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).
Re: Vite 8.0 Is Out
#33Vite 8 is pretty incredible. We saw around an 8x improvement (4m -> 30s) in our prod build, and it was nearly a drop-in replacement. Congrats (and thank you!) to the Vite team!
4 minutes?! How large is that app?
Not meant as a gotcha but I'm surprised because people always tout it as being so much faster than Next. (4m with Turbo would have to be a crazy huge app IME)
Re: Vite 8.0 Is Out
#34[dead]
Re: Vite 8.0 Is Out
#35Earlier 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?
I'm being rather snarky here, but the main point of front-end JS UI frameworks is to exist and to survive in their environment. For this purpose they have evolved to form a parasymbiotic relationship with others in their environment, for example with influencers. The frameworks with the best influencers win out over older ones that do not have the novelty value anymore and fail to attract the best influencers.
This could also apply to the recent wave of hate towards Next.
Re: Vite 8.0 Is Out
#36Earlier quoted context omitted.
After Tanstack Start, Next.js seems even less intuitive. While it remains a viable option due to its established momentum, it feels quite alien to backend devs, esp with its unconventional defaults.
It feels like Wordpress inasmuch as it’s shoving a tool in places that don’t make sense. React is great for SPAs but if I wanted pre-rendered static content I’d use a different tool.
I had had a client cancel a job when they heard it's not going to use Wordpress. It was going to be a dashboard showing statistics (air quality, room bookings etc.) from their facility.
Re: Vite 8.0 Is Out
#37Re: Vite 8.0 Is Out
#38Vite 8 is pretty incredible. We saw around an 8x improvement (4m -> 30s) in our prod build, and it was nearly a drop-in replacement. Congrats (and thank you!) to the Vite team!
Same here (10s to 1s). The main reason for this is rolldown [1]. Already had it installed months ago, before it got merged into vite proper. Really awesome stuff.
Re: Vite 8.0 Is Out
#39Earlier quoted context omitted.
Why go halfway, embrace compiled languages in the backend. Fast all the way down, especially when coupled with REPL tooling.
Because writing Rust backend is needlessly complex for majority of projects.
I've had a great time using Rust with Actix as the framework.
Re: Vite 8.0 Is Out
#40Earlier quoted context omitted.
Why go halfway, embrace compiled languages in the backend. Fast all the way down, especially when coupled with REPL tooling.
Because writing Rust backend is needlessly complex for majority of projects.
Still easier than dealing with node dependencies, webpack and co, they make me wish to write ASP with OCX components instead.