The absurd complexity of server-side rendering
gist.github.com
The absurd complexity of server-side rendering
1–10 of 395 posts
Re: The absurd complexity of server-side rendering
#2The complexity of web development frontend itself is just absurd. The mess of dependencies, the mess of language transpiling, opaque abstract functions with unreadable call stacks, asset management, sync vs async, the random best practice of the week, etc.
I look at the state of web pages and apps and it's not even for the betterment of user experience! Hacker News and old.reddit.com still provide the smoothest, fastest experience at the cost of having to zoom in every once in a while, but the price is worth it.
Re: The absurd complexity of server-side rendering
#3The complexity of web development frontend itself is just absurd. The mess of dependencies, the mess of language transpiling, opaque abstract functions with unreadable call stacks, asset management, sync vs async, the random best practice of the week, etc. I look at the state of web pages and apps and it's not even for the betterment of user experience! Hacker News and old.reddit.com still provide the smoothest, fast…
I handwrite all my CSS directly in the browser and the only "dependency" I use is a reset.css. The zooming issues some of those old themes have can all be solved with a modern css grid template (one for smartphone, one for desktop). Needless to say sites like these can be blazing fast.
I only use js for small things like maybe hiding some header when scrolling down (no jquery, handwritten vanilla js with maybe 20 linws of code), but even that would not be strictly needed.
Re: The absurd complexity of server-side rendering
#4throw all that complicated stuff away & use htmx
generate html the same ol’ way you always have
safe & effective modern hypermedia
Re: The absurd complexity of server-side rendering
#5Call me old fashioned, but PHP still gets the job done better than just about anything else.
Re: The absurd complexity of server-side rendering
#6The complexity of web development frontend itself is just absurd. The mess of dependencies, the mess of language transpiling, opaque abstract functions with unreadable call stacks, asset management, sync vs async, the random best practice of the week, etc. I look at the state of web pages and apps and it's not even for the betterment of user experience! Hacker News and old.reddit.com still provide the smoothest, fast…
My org just bought a professional bootstrap template. It takes 3 build tools and 1500 node packages just to build the SASS into a CSS bundle. It boggles my mind that this is normal in the front end world.
Re: The absurd complexity of server-side rendering
#7Call me old fashioned, but PHP still gets the job done better than just about anything else.
And usually leads to a BBOM architecture
Re: The absurd complexity of server-side rendering
#8The complexity of web development frontend itself is just absurd. The mess of dependencies, the mess of language transpiling, opaque abstract functions with unreadable call stacks, asset management, sync vs async, the random best practice of the week, etc. I look at the state of web pages and apps and it's not even for the betterment of user experience! Hacker News and old.reddit.com still provide the smoothest, fast…
My org just bought a professional bootstrap template. It takes 3 build tools and 1500 node packages just to build the SASS into a CSS bundle. It boggles my mind that this is normal in the front end world.
only 1500? you got lucky!
gatsbyjs (React framework) has so many dependencies it breaks GitHub's dependency graph
Re: The absurd complexity of server-side rendering
#9Hum... You mean JS needs generic monads?
TypeScript supports them, doesn't it? This shouldn't be too hard to fix, but it's a matter of rewriting or encapsulating all of the core language's API.