Readit NewsSmooth transitions are a nice side effect, but not the reason for an SPA. The core argument of the article, that client-side routing is a solution for page transitions, is a complete misunderstanding of what problems SPAs solve. So absolutely, if you shared that misunderstanding of SPAs and used them to solve the wrong problem, this article is 100% correct.
But SPAs came about in the days of jQuery, not React. You'd have a complex app, and load up a giant pile of jQuery spaghetti, which would then treat each div of your app is its own little mini-app, with lots of small network requests keeping everything in sync. It solved a real problem, of not wanting to reload all that code every time a user on an old browser, with a slow connection, changed some data. jQuery made it feasible to do SPAs instead.
Later, React and other frameworks made it less spaghetti-like. And it really took off. Often, for sketchy reasons. But the strongest argument for SPAs remains using them as a solution to provide a single-load of a large code bundle, that can be cached, to provide minimal network traffic subsequent to the load when the expected session time of a user is long enough to be worth the trouble of the complexity of an SPA.
...and yet, i keep running into web (and even mobile apps) that load the bundle, and subsequent navigation is just as slow, or _even slower_. Many banking websites, checking T-Mobile balance... you wait for the bundle to load on their super-slow website, ok, React, Angular, hundreds of megs, whatever. Click then to check the balance, just one number pulled in as tiny JSON, right? No, the website starts flashing another skeleton forever, why? You could say, no true SPA that is properly built would do that, but I run into this daily, many websites and apps made by companies with thousands of developers each.
I have enjoyed the github copilot agent style development where someone elses computer is running everything, and I can make a request and just come back half an hour later and check on it. But this level 5 driver gets the wrong destination basically every time, and then it's another 10, 20 or even 30 minutes for it to make a minor adjustment. It doesnt understand my `yarn` scripts, it runs my tests wrong, it can't do codegen, it doesn't format or lint files, etc. I asked copilot yesterday to lint and format a PR and it took 25 minutes of agentic work lol.
I would think that's the process too, but according to the article the dude is almost completely hands off:
> You come back to ten thousand lines of code. You spend 5 minutes reading. One sentence of feedback. Another ten thousand lines appear while you're making lunch.
You can't humanly review 10 thousand lines of code in 5 minutes. This is either complete bullshit or it really writes flawless code for them and never makes any mistakes.
wait, i thought it was Watson that was supposed to replace me
It is really the same kind of thing.. but the model is "smarter" then a junior engineer usually. You can say something like "hmm.. I think an event bus makes sense here" Then the LLM will do it in 5 seconds. The problem is that there are certain behavioral biases that require active reminding (though I think some MCP integration work might resolve most of them, but this is just based on the current Claude Code and Opus/Sonnet 4 models)
lol sounds like a true nightmare. Code is a liability. Faster junior coding = more crap code = more liability.
I mean... like you said, the genie is already out of the bottle, I don't get it.
Secondly, yes, it was likely a deliberate action to cut off the fuel switches, as you say.
You are absolutely right that there’s an epidemic in the airline industry that forces pilots to stay quiet rather than risk their careers if they’re dealing with mental health issues.
In a sibling comment: “shouldn’t they be given alternate career paths?” No. Perpetuating the myth that people with mental health issues are somehow broken beyond repair is mistaken. Current policy lead directly to that one fellow to lock the cockpit door and slam the plane into a hillside. If Air India 171 has any chance of being a mental health issue today, it should be highlighted and explored. You’re exactly right to be doing that, and thank you.
Anyone who disagrees with this should watch https://youtu.be/988j2-4CdgM?si=G39BwNy1zJEeUi2k. It’s a video from a well-respected pilot. The whole point of the video is that aviation forces people to conceal their problems instead of seek treatment, and that this has to change.
While obviously the incidents are terrible, do you really think he would self-report, voluntarily endure 6+ months of therapy and come back like new, if only the current policy didn't lead him to do what he did?
Totally armchair, but I think people like the German dude and allegedly (but who knows) the Malaysian Zaharie are far gone. The only thing that can help is mandatory health checks, and even then who knows if it's possible to screen for everything.
What are they building? A training corpus.
Are people who responds to their ads getting the money for free?
Handing your codebase to an AI company is not nothing.
it's a battle that's already lost a long time ago. Every crappy little service by now indexes everything. If you ever touch Github, Jira, Datadog, Glean (god forbid), Upwork, etc etc they each have their own shitty little "AI" thing which means what? Your project has been indexed, bagged and tagged. So unless you code from a cave without using any saas tools, you will be indexed no matter what.