🫠 CSS-in-JS: The Great Betrayal of Frontend Sanity
｢ CSS-in-JS was born out of good intentions — modularity, predictability and componentization. But what we got was complexity disguised as progress. The web didn’t need runtime styling engines or cryptic hashes to stay modern. It needed restraint. It needed developers willing to accept that not every problem requires a library ｣
https://thenewstack.io/css-in-js-the-great-betrayal-of-frontend-sanity/
The untold history of web development:
1990: HTML invented.
1994: CSS invented to fix HTML.
1995: JS invented to fix HTML/CSS.
2006: jQuery invented to fix JS.
2010: AngularJS invented to fix jQuery.
2013: React invented to fix AngularJS.
2014: Vue invented to fix React & Angular.
2016: Angular 2 invented to fix AngularJS & React.
2019: Svelte 3 invented to fix React, Angular, Vue.
2019: React hooks invented to fix React.
2020: Vue 3 invented to fix React hooks.
2020: Solid invented to fix React, Angular, Svelte, Vue.
2020: HTMX 1.0 invented to fix React, Angular, Svelte, Vue, Solid.
2021: React suspense invented to fix React, again.
2023: Svelte Runes invented to fix Svelte.
2024: jQuery still used on 75% of websites.
(By https://twitter.com/fireship_dev)
#Web #Development #HTML #CSS #JavaScript #React #ReactJS #JQuery #Svelte #Angular #AngularJS
RCE Vulnerability in React and Next.js
https://github.com/vercel/next.js/security/advisories/GHSA-9qr9-h5gf-34mp
#HackerNews #RCE #Vulnerability #in #React #and #Next.js #ReactJS #NextJS #Vulnerability #Cybersecurity #SoftwareSecurity
🥊 React vs Backbone in 2025
｢ The Backbone code is brutally honest about what it's doing. An event fires, a handler runs, you build some HTML, you put it in the DOM. It's verbose, sure, but there's no mystery. A junior developer can trace exactly what happens and when. The mental model is straightforward: "when this happens, do this."
The React code hides a lot ｣
🌩️ A deep dive into Cloudflare’s September 12, 2025 dashboard and API outage
｢ The API calls were managed by a React useEffect hook, but we mistakenly included a problematic object in its dependency array. Because this object was recreated on every state or prop change, React treated it as “always new,” causing the useEffect to re-run each time. As a result, the API call executed many times during a single dashboard render instead of just once ｣
https://blog.cloudflare.com/deep-dive-into-cloudflares-sept-12-dashboard-and-api-outage/
