recentpopularlog in

dirtystylus : reactjs   85

« earlier  
Andy Bell on Twitter: "If we bake React into the browser, do we bake the toxic masculinity, links with a cesspit social network and the under-representation of folks who aren’t CIS-men? Or was it just the component model and diffing that you want?"
If we bake React into the browser, do we bake the toxic masculinity, links with a cesspit social network and the under-representation of folks who aren’t CIS-men?

Or was it just the component model and diffing that you want?
reactjs  browser  techculture 
11 weeks ago by dirtystylus
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
Andrew Clark on Twitter: "So many update performance problems in React go away when you use local state. If you have some state that updates frequently and needs to be fast (ahem, forms), probably shouldn't be putting that in a global store that the whole
So many update performance problems in React go away when you use local state.

If you have some state that updates frequently and needs to be fast (ahem, forms), probably shouldn't be putting that in a global store that the whole app subscribes to!
codearchitecture  reactjs  javascript  statemanagement 
september 2018 by dirtystylus
verekia/js-stack-from-scratch: 🛠️⚡ Step-by-step tutorial to build a modern JavaScript stack.
This is a straight-to-the-point guide to assembling a JavaScript stack. It requires some general programming knowledge, and JavaScript basics. It focuses on wiring tools together and giving you the simplest possible example for each tool. You can see this tutorial as a way to write your own boilerplate from scratch. Since the goal of this tutorial is to assemble various tools, I do not go into details about how these tools work individually. Refer to their documentation or find other tutorials if you want to acquire deeper knowledge in them.
tutorial  javascript  tools  webdev  via:swarshbucklin  reactjs  react  buildtools  npm  yarn  webpack 
may 2017 by dirtystylus
jevakallio/redux-offline: Build Offline-First Apps for Web and React Native
Redux Offline is very, very new. If you find a bug, good job for being an early adopter!
via:peter_chappy  offline  offlinefirst  reactjs  redux  github 
march 2017 by dirtystylus
« earlier      
per page:    204080120160

Copy this bookmark:





to read