3 ms·

Here's hoping Web 3.0 goes back to minimalism. Unless you're building a fully interactive web application, let's get back to server side rendering, optimized im

Here's hoping Web 3.0 goes back to minimalism. Unless you're building a fully interactive web application, let's get back to server side rendering, optimized images, and minimal web requests. Now that everyone is getting faster and faster internet speeds, the web has turned into the old sloppy coding practices, where CPU speeds were doubling year after year. Just give me the information we need without all of the magical fluff around it.

highesttide 8y ago
I honestly don't think I would want to keep working with webdev if I had to go back to relying on server side rendering for everything, the workflow is just _so_ much worse (to me).
- pjc50 8y ago
  Why is that, do you think?
- overcast 8y ago
  Your priority as a developer, shouldn't be what is best for you, it should be what is best for your end user.
- rpdillon 8y ago
  I'd like to hear more about your experience. I was in a technical presentation yesterday in which a web developer working on a Rails codebase that has been transitioning from backbone to React over the past couple of years talked about her experience trying to add a single page to the app. In the end, it required 14 steps, and I couldn't help but wonder whether all the scaffolding, code generation, and wiring to enable both dynamic and static rendering to work correctly (static for search engines) really provides a better experience for anyone. I get why companies like Google and Facebook developed these frameworks, but for a site of moderate size (say, a million monthly uniques), is it really a win? I look at sites like https://pinboard.in/ https://pinboard.in/ and feel like they really hit the sweet spot on utility, user experience, performance, and development workflow. But most of my experience is on the backend. What am I missing?
TeMPOraL 8y ago
Fully agree with you, I want the same things. Sadly, TFA is not about this. TFA is about even more bloated Internet, backed by one the most ridiculous way of wasting energy ever invented.

highesttide 8y ago

I honestly don't think I would want to keep working with webdev if I had to go back to relying on server side rendering for everything, the workflow is just _so_ much worse (to me).

pjc50 8y ago
Why is that, do you think?
overcast 8y ago
Your priority as a developer, shouldn't be what is best for you, it should be what is best for your end user.
rpdillon 8y ago
I'd like to hear more about your experience. I was in a technical presentation yesterday in which a web developer working on a Rails codebase that has been transitioning from backbone to React over the past couple of years talked about her experience trying to add a single page to the app. In the end, it required 14 steps, and I couldn't help but wonder whether all the scaffolding, code generation, and wiring to enable both dynamic and static rendering to work correctly (static for search engines) really provides a better experience for anyone. I get why companies like Google and Facebook developed these frameworks, but for a site of moderate size (say, a million monthly uniques), is it really a win? I look at sites like https://pinboard.in/ https://pinboard.in/ and feel like they really hit the sweet spot on utility, user experience, performance, and development workflow. But most of my experience is on the backend. What am I missing?

TeMPOraL 8y ago

Fully agree with you, I want the same things. Sadly, TFA is not about this. TFA is about even more bloated Internet, backed by one the most ridiculous way of wasting energy ever invented.