terandle

Wow a human employee in walmart in 2040, very optimistic take.

Yeah Vite+Reat+Tanstack SPA apps is definitely the way to go for a majority of web apps. I would still stick with nextjs for ecommerce or pages that need to load instantly when clicked from google however.

It's a good idea in theory, the perf just needs to be better. Maybe with bun.

I'm anti-establishment because the establishment doesn't care about anyone but themselves. What are we doing all this work for? Progress would be getting universal healthcare for all in this country. Getting better work life balance. Being able to afford a home. Now it's just all the "haves" fighting bitterly to keep getting more and more until they have everything and nothing for anyone else.

> Think of it like WWII, only only instead of planting victory gardens to beat the Nazis, we're building AI apps and finding ways to create the economic value needed to cover the reckless bets being made by the elites.

LOL fuck this, the stock market deserves to burn to the ground.

I think HN is it's own anti-react bubble that really doesn't match reality. Everyone here decided they hated react in 2016 or whatever and doesn't want to update their worldview to the reality that react is frankly an amazing tool today.

Kind of sad to see a 2022 paper about svelete with extremely questionable benchmarks get upvoted so much vs all the great things that came out of react conf yesterday.

Have had our apps on expo for a while. Highly recommend, much easier upgrades and you can turn off any platform vendor stuff like their OTA updates and do local builds also. Expo + RN has saved us a ton of time on our apps and no way a small team like us could support both platforms otherwise.

Performance of WASM issues. Rendering performance of large data grids is not good. Also the first load time is also terrible 50mb+ payloads.

Blazor server uses websockets and is just a whole other bag of hurt. You'll have to deal with disconnects even if you can stomache the increased cloud costs.

Blazor is not good at anything. Please stick with JS for the frontend .NET devs. You'll thank me later.

Yeah there is basically no real difference between MVC or RazorPages or BlazorStaticServer pick your poison depending on your preference. Personally I wish the .NET team would just add components to MVC and RazorPages then we can forget about Blazor.

Blazor static server side + HTMX is probably the only way to make a cost efficient and performant version of Blazor suitable for public websites. WASM is way too big and slow, Websockets take up server resources and cause problems with timeouts where the user has to refresh their screen losing all state.

Seems like Linus should be able to tap someone else to do 6.17 while he is on vacation

I think nextjs does lead to a very simple codebase at every step of the interactivity gradient. You can have pure server side rendered HTML all the way up to full blown SPA and everything inbetween with just one tool rather than having...

1. HTMX itself

2. Your backend language Go/Java/whatever

3. Whatever JS framework for your interactivity islands

But yes we are all on the same team here of reducing complexity in the codebase and if HTMX works for you go for it.