dirtystylus + nodejs   33

Disenchantment - Tim Novis
After years of working in SPA-land, rarely touching a server-rendered website, I was amazed at how quick it was to get up and running and start feeling productive right away. Developers are quick to extoll the virtues of tools like Create React App, and whilst I agree - they’re great! It really takes a while to start feeling productive when setting up a new SPA from the ground up. So much non-work has to be done before the real work, what you’re likely being paid to do, can begin.

I had an admin panel with authentication, pages, routes, templates and CSS, flash messaging, The Works™️ set up in an afternoon. I hadn’t felt this productive in years. But best of all, it was fun. Of course I still enjoy working with our modern, flashy tech stack - but this felt so different. No waiting for recompilation. No React devtools. No props and state flying around. No convoluted centralised state management. No worrying about loading states. Complete bliss. It was functional, it was fast, and it felt solid. The only thing I legitimately missed from a “developer experience” perspective was TypeScript. TypeScript is great, and gives me much more confidence when shipping code.

I would urge front-end developers to take a step back, breathe, and reassess. Let’s stop over engineering for the sake of it. Let’s think what we can do with the basic tools, progressive enhancement and a simpler approach to building websites. There are absolutely valid usecases for SPAs, React, et al. and I’ll continue to use these tools reguarly and when it’s necessary, I’m just not sure that’s 100% of the time.
programming  javascript  webdev  tools  nodejs  reactjs  backend 
may 2019 by dirtystylus
Learn JavaScript Universal… by Eric Elliott [PDF/iPad/Kindle]
Want to learn about universal app development with Node, ES6, & React? I've got you covered:
book  javascript  nodejs  reactjs  from twitter_favs
june 2015 by dirtystylus

Copy this bookmark: