This comment thread is a little funny because every single HN thread outside of this one rants super aggressively about webpages that don't show any content before JS loads, but this thread has managed to collect the opposite group together for once because React's docs have updated to stop actively recommending tools that force that problem to happen.
New React docs pretend SPAs don't exist anymore
71–80 of 225 posts
Re: New React docs pretend SPAs don't exist anymore
#72Earlier quoted context omitted.
Why do I hear so much about htmx and so little about unpolly, which seems everything htmx promise but with additional high level primitives for the common task?
Unpoly dev is german nobody cares about abd doesnt go on podcasts vs htmx author is american that does marketing well. Same goes for alpine js where the author is “famous” dev. Pretty typical with open source projects tbh. Many of them win thanks to marketing more than anything else.
Re: New React docs pretend SPAs don't exist anymore
#73I love the potential of web development but of recent, it's been infected by hype-marketing and blog-engineering.
I get that it's become very accessible to write web applications and that's good for the growth of the platform - but it almost feels like this accessibility has led it to squander its potential in pursuit of unsophisticated and unambitious objectives.
Web developers today are distracted by premature over-optimisations (ignoring effective low effort optimisations) and language+platform features that are a great, but kinda useless from a project development standpoint (time/money/complexity/collaborative capacity cost).
As a result, platform developers are distracted implementing features that don't innovate the platform - so we sit and wait for the truly groundbreaking things that never come because we gotta discuss the pipe operator, or adding types to the JavaScript language specification.
Meanwhile projects that can't wait for the platform to evolve flood us with Electron apps that everyone hate.
I have hope, kinda...
Re: New React docs pretend SPAs don't exist anymore
#74no i dont need ssr at all, internal tools,dashboards,embedded devices,etc etc have nothing to do with ssr,nothing at all
Re: New React docs pretend SPAs don't exist anymore
#75Re: New React docs pretend SPAs don't exist anymore
#76It’s disappointing to me they’ve gone so hard on server side.
It feels like Facebook use it server side so they’ve lost interest in being purely client side.
Re: New React docs pretend SPAs don't exist anymore
#77Re: New React docs pretend SPAs don't exist anymore
#78Re: New React docs pretend SPAs don't exist anymore
#79Earlier quoted context omitted.
Why do I hear so much about htmx and so little about unpolly, which seems everything htmx promise but with additional high level primitives for the common task?
Unpoly dev is german nobody cares about abd doesnt go on podcasts vs htmx author is american that does marketing well. Same goes for alpine js where the author is “famous” dev. Pretty typical with open source projects tbh. Many of them win thanks to marketing more than anything else.
Re: New React docs pretend SPAs don't exist anymore
#80So after graphql, micro services, nosql and serverless, the SPA + "libs not framework" crowd join the "woooops!" club. Ignoring the noise is really becoming a key skill to survive as a programmer.