The Vercel incident might feel "funny" to outsiders, but it's just another nail in the coffin of full stack JavaScript.
With Remix pivoting every year and nextjs making the oddest decisions, in 2026 the most sensible option for a new project is Tanstack Start. A framework in RC.
Spot on. The maintainability suffers when you stop being paranoid and you don't pilot it properly. At that point you wonder, why am I working backwards? Correcting instead of writing?
im fully convinced that LLMs are not an actual net productivity boost (today)
they remove the barrier to get started, but they create increasingly complex software which does not appear to be maintainable
so far, in my situations, they appear to slow down long term velocity
@OfTheTaco You can't have collectable nature so early and also expect the game to grow. I can be wrong. Long term your first prints will regain value. I hope it will be better. Our local scene was fading before but people are joining en masse now.
@neogoose_btw The issue was getting continuous updates, new templates, sites, component libraries for free! Who pays the engineers? I loved that for me as a customer, but it didn't sound sustainable.
@codetrap_dev Agreed. Centralized state with rxjs for orchestration worked nicely for me. Still I felt I was fighting react here and there but much better than the alternatives.
Itβs wild how little sticks around when someone hits a server with the #React RCE payload. All the interesting parts of the POST request live for a moment in memory, get decoded, executed (or rejected), and vanish. Nothing hits a log, nothing lands on disk.
You can scan process memory for patterns, sure, but youβll mostly catch scanners, broken requests, bots, random noise. A clean βthis was a successful exploitβ signal isnβt really possible here. The only reliable detection is post-exploitation activity on the box.
Super fun vuln to hunt forβ¦ not π
I'll continue to die on the hill of "magic directives are bad API interfaces". They're not type-safe, they're not extensible, no native runtime control, they're just strings.
... I can't believe I'm saying this, but I would rather debate @ directives. Pls rewind history.
@src_rip Query solves some annoyances with the lifecycle of React. It shines when you want to cache stuff and invalidate on network change, tab focus, and others.
Handles paginated/cursor queries out of the box, so generally a good deal of functionality you'll build can be offloaded.