Hacker News new | past | comments | ask | show | jobs | submit login

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).



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/ 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?


Your priority as a developer, shouldn't be what is best for you, it should be what is best for your end user.


Why is that, do you think?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: