When did the industry transition to different/lead free solders? Wonder if that was part of the issue?

Yeah, it was the transition to RoHS.

Oh do tell.

I think this reply might have been downvoted for being a bit glib, but the superpowers plugin took my Claude Code experience from mostly frustrating to nearly-magical

I’m not a software engineer by training nor trade, so caveats apply, but I found that the brainstorming -> plan writing -> plan execution flow provided by the skills in this plugin helps immensely with extracting assumptions and unsaid preferences into a comprehensive plan—-very similar to the guidance elsewhere in this thread, except automated/guided along by the plugin skills

Try this one: https://youtu.be/Yl1FNX08HFc

No.

>This was me in 2005.

Ha, same. Windows XP for me had a horrible habit of booting into a blue screen randomly after updating video card drivers (happened with both ATI and Nvidia). Trying to do a repair install wouldn't work. The only option was a full reinstall.

Installation from the disk took an hour. Then (if you were going about this the legal way) you'd have to call the microsoft number to register your install, but be on hold for another 30 minutes. Then it was multiple hours of install your favorite video player, reboot. Install video codecs, reboot. Install firefox, reboot. Apply all of your registry tweaks, reboot. Install all your games from CD-ROM, more rebooting. And multiple hours of that.

I moved to linux back in 2006 or so and never looked back. Documented part of the journey here https://net153.net/ubuntu_vs_debian.html

> My proposition for compatibility is to not use dependencies, and instead rely on the standard library

Funny that was the whole attack angle python used against perl back in 2005,etc.

>Timing it for Christmas Eve ensures minimal media scrutiny of these connections.

Sounds like the media is truly the one in charge.

So this is part of the "React2Shell" CVE-2025-55182 issue? I find it interesting that this seems to get so little publicity. Almost like the issue is normal or expected. And it looks like the affected versions go back a little over a year. So if you've deployed anything with Next.js over the last 12 months your web app is now probably part of a million node bot net. And everyone's advice is just "use docker" or "install a firewall".

I'm not even sure what to say, or think, or even how to feel about the frontend ecosystem at this point. I've been debating on leaving the whole "web app" ecosystem as my main employment ventures and applying to some places requiring C++. C++ seems much easier to understand than what ever the latest frontend fad is. /rant

Frontend churn has chilled out so much over the last few years. The default webapp stack today has been the same for 5 years now, next.js (9yo) react (12yo) tailwind (8yo) postgres (36yo). I'm not endorsing this stack, it just seems to be the norm now.

Compare that to what we had in the late 00's and early 10's we went through prototype -> mootools -> jquery -> backbone -> angularjs -> ember -> react, all in about 6 years. Thats a new recommended framework every year. If you want to complain about fads and churn, hop on over to AI development, they have plenty.

I remember that. To be honest it was exhausting. Fun, but exhausting. It’s nice now to have found a stack that is “just fine” for most things.

You can write web apps without touching the hottest JS framework of the week. I've never touched these frameworks that try to blur the line between frontend and backend.

Pick a solid technology (.NET, Java, Go, etc...) for the backend and use whatever you want for your frontend. Voila, less CVEs and less churn!

I had a Pangolin instance compromised by this: https://github.com/orgs/fosrl/discussions/2014

I'm hearing about it like crazy because I deployed around 100 Next frontends in that time period. I didn't use server components though so I'm not affected.

My understanding of the issue is that even if you don't use server components, you're still vulnerable.

Unless you're running a static html export - eg: not running the nextjs server, but serving through nginx or similar

Yeah, crucially it says

> If your app’s React code does not use a server, your app is not affected by this vulnerability. If your app does not use a framework, bundler, or bundler plugin that supports React Server Components, your app is not affected by this vulnerability.

https://react.dev/blog/2025/12/03/critical-security-vulnerab...

So if you have a backend that supports RSC, even if you don't use it, you can still be vulnerable.

GP said they only shipped front ends but that can mean a lot.

Edit:link

They might be referring to another Vercel vulnerability that allowed anyone to bypass their auth with relative ease due to poor engineering practices:

https://nvd.nist.gov/vuln/detail/CVE-2025-29927

That plus the most recent react one, and you have a culture that does not care for their customers but rather chasing fads to help greedy careers.

For my Java based sites, I use HTML/CSS/JS (vanilla js), no frameworks.

Use Svelte? (:

I would read the manual too on the ride home. But I think that was only for new games? I seem to remember that rentals didn't come with manuals. The best memory was my grandma picking me up to spend the summer at her house. We stopped by wal-mart and I grabbed the first release of Gran Turismo for psx. It came with a fairly giant manual. Had a three hour drive to her house. I read it over and over!