I've been working with React Native for about two years now and have really been trying to give it the benefit of the doubt. I'm done with that. RN is garbage.
I've been having too much fun clipping things on YouTube to share with my colleagues. Here's a clip with @slightlyoff on questions you should ask yourself when considering React:
Has anyone here got opinions about Preact vs React?
Specifically, I'm weighing up migrating a large-ish codebase to Preact instead of upgrading React, and I'd be interested to hear from anyone who a) has done this, b) has decided not to do this, c) can think of solid reasons to stick with React.
I can't see much benefit to choosing React over Preact, but is there anything I'm overlooking?
About every time I think about an architectural problem in a #react application, I think: "This could easily be solved using a context!". Then I remember that the context API does not work with react server components and I'm lost.
I wrote up a small article on how to structure providers in #react. By splitting data in to different providers you can save a lot of render time around the app.
The story of my life when developing some web project is mostly always the same: I can surf on the code waves for a while... And then some apparently minor, silly detail got me stuck for hours. Now it's been a Vue component that refuses to display a selected placeholder by default, so you don't have to stare at an empty select bar. Yes, I've tried that already but no dice. Will I make it? Yeah, or bust. :D
"I hate it. There are so many things wrong with #React. The cult surrounding it, the company making it, its countless footguns, its bloat, its incompatibility with web platform features—the list goes on."
Looking for some feedback from #webdev folks.. I'm experimenting with migrating a #nextjs project to Astro. On paper, the site is a great candidate - content-focused (blog, articles) looking for lighter client experience and better dev experience. https://astro.build/
I have a CMS wired up and have started migrating a couple React components. What gotchas are hiding deeper in this project? Where are the common pitfalls with Astro?
For nearly a decade I was a strong fan of using jQuery and Backbone to enhance server generated html.
What led me to abandon that and embrace #React was not reactive development, it wasn’t the performance of dom diffing, it wasn’t any of the things that were inherent to React… it was JSX and pluggable, composable components.
Now, after two years working in a large scale react SPA with federated microfrontends… I’m finding that I miss the simplicity of Backbone and jQuery.
Created 65 tickets to migrate from class components to functional , some are small and should be relatively easy others are 2000+ mono components that render whole pages. Legacy #React is such a trip (I’m sure I’m also responsible for similar code in a past life)
Skew Protection solves two problems with frontend applications:
If users try to request assets (like CSS or JavaScript files) in the middle of a deployment, Skew Protection enables truly zero-downtime rollouts and ensures those requests resolve successfully.
Outdated clients are able to call the correct API endpoints (or React Server Actions) when new server code is published from the latest deployment.
My engineering team inside the WP Engine marketing department is looking for another dev to join us! Someone into modern #WordPress dev, but also knows their way around #React, with a can-do attitude in a fast paced environment. Who's interested?
"This reminds me of a hammer I had with a broken handle. Instead of replacing the handle, I attached the hammer to a helmet and whenever I want to drive a nail, I would wear the hammer and swing my head. But sometimes I miss and hit my head against the wall instead. So to fix that, I added some padding to my forehead and now it doesn’t hurt at all.