Look, I’m in no position to talk seeing as I once wrote a cron job in PHP, but the profusion of JavaScript in the late aughts and early teens for things that weren’t “make my website prettier!” feels very much like a bunch of “webmasters” dealing with the fact that the job market had shifted out from under them while they weren’t looking and rebranding as “developers” whose only tool was Hammer.js, and thinking all their problems could be recontextualized as Nail.js.

Point me towards systems that don’t have a human in the loop, particularly any that utilize fully-autonomous swarms, and I’ll agree. Scary as the former are, there’s a world of difference between a handful of FPV suicide drones, and a cloud of HL2-Manhack-esque things operating on face-recogniton-guided autopilot.

I’ve low-key started to think the only reason we haven’t seen autonomous hunter-killer drones yet is that nobody’s willing to break the seal, and I’m scared for what happens when somebody finally does.

I was the last of my immediate family on Facebook, and I only stuck around to keep in touch with a couple hobby groups. I decided to cut the cord once Zuck went mask-off, and honestly I haven’t regretted it. The family group text is still chugging along fine, and most of the people I actually want to talk to are on other platforms at this point.

I don’t blame anybody who feels like they have to keep Facebook to stay in touch with loved ones… but man, it feels good not to have that spammy time suck on my phone anymore.

Nobara is just Fedora with a heavy layer of gaming-focused polish applied. In that regard it’s quite a bit more familiar than something like Arch, which makes a point of not holding anybody’s hand, and (just in terms of ease of use and overall userbase) feels a lot closer to what Gentoo was like back when I last was in this space.

I was heavily in the camp of Debian-based distros back in the day, but Debian proper has never been a great choice for desktop, and Ubuntu’s star is much faded of late, so I decided to give an RPM-based distro a chance before jumping way off into the deep end. I don’t have the time to fiddle that I used to, and (at least until yesterday’s hiccup) Nobara was much closer to “it just works” out of the box than anything like Arch would have been.

I’m an ex-sysadmin so I guess I get to be the middle head, but blundering my way through the current distro scene after not having touched a desktop Linux install in, oh… twenty years or so, I feel more like the right. I suppose on the one had I had the good sense not to jump right into Arch or Nix, but even more familiar territory like Nobara has its pitfalls. Just today I had to clean up a botched release upgrade because the primary maintainer had left conflicting packages in the repository for an extended period. Not laying blame per se, that’s what you get when you sign on to a one-man effort, but it was a real pain in the butt to diagnose and correct.

Say it with me now: model collapse! I think this approach is especially insidious in that rather than dumping obvious nonsense into the training corpus that can then be scrubbed, it pushes the downstream LLM invisibly towards spontaneously imploding.

737s don’t have RATs. According to some 737 pilots I’ve seen commenting, the APU is operable in flight, but doesn’t kick in automatically and would have required ~60 seconds to start. The main electrical generators don’t automatically restart after tripping, either, so a scenario where electric power is hypothetically available, but a panicked or overloaded flight crew don’t take the steps to bring it online, is plausible.

Hydraulics and electric system are independent in commercial aircraft – hydraulic pumps are directly driven from the engines, as are electrical generators. Redundancy is provided via independent loops/buses from each engine. A bird strike on its own is unlikely to be energetic enough to sever one of those independent systems, let alone all four. Losing both engines could do it, – but again, they had enough thrust to attempt a go-around, so they weren’t a glider immediately after the bird strike. The 737 is an old-school design, too, so most critical components have full manual reversion – as long as you have airspeed and altitude enough to get to the runway, you can fly and land the plane just with cable controls and manual releases in the event of total electric and hydraulic failure.

I did a bit of reading from other sources and this particular aircraft predates the requirement for battery backup of the FDR and CVR, and the APU does not start up automatically on a power failure, so the failure chain for that part of the incident isn’t as long as I initially thought. Still, lots of questions, and I think the simplest explanation so far is the aircrew panicking and making a survivable situation into a bloodbath.

Everything about this incident is just so fucking odd. That a bird strike could take out both engines isn’t unheard of (see US Airways Flight 1549) but I’ve heard reports that there was a failed emergency landing attempt before the one that we saw video of, so they clearly had thrust enough to stay in the air for a go-around, and from the video we saw they carried in a ton more speed than I would expect if there had been catastrophic damage to both engines.

Except that the lack of landing gear suggests loss of hydraulic power from both engines… Except there is an emergency release that drops the gear on a 737 with just gravity, and there’s no evidence this was even attempted.

Now it looks like some electrical systems, including power to the data recorders, died right at the start of the incident, which would require not just double engine failure but failure of the APU and backup battery systems. That just seems incredibly unlikely.

Catastrophic electrical failure several minutes before the crash, though, would suggest that it wasn’t just a case of a panicked aircrew making a chain of bad decisions, which was my initial read of the situation and maybe the best fit for the rest of the circumstances.

I just can’t think of a chain of events that could reasonably lead to all the failures in evidence while still allowing the aircraft to remain airworthy for two landing attempts.

And then you get to the horrifying fact that a relatively new and modern airport had a giant concrete obstacle in what would be considered the Runway Safety Area at a US facility… Like, what the fuck? That seems like it’s designed to create this sort of a disaster.

Keep in mind that when 10nm was in planning, EUV light sources looked very exotic relative to current tech, and even though we can see in hindsight that the tech works it is still expensive to operate – TSMC’s wafer costs increased 2x-3x for EUV nodes. If I was running Intel and my engineers told me that they thought they could extend the runway for DUV lithography for a node or two without sacrificing performance or yields, I’d take that bet in a heartbeat. Continuing to commit resources to 10nm DUV for years after it didn’t pan out and competitors moved on to smaller nodes just reeks of sunk-cost fallacy, though.

Intel’s problems, IMO, have not been an issue of strategy but of engineering. Trying to do 10nm without EUV was a forgivable error, but refusing to change course when the node failed over and over and over to generate acceptable yield was not, and that willful ceding of process leadership has put them in a hole relative to their competition, and arguably lost them a lucrative sole-source relationship with Apple.

If Intel wants to chart a course that lets them meaningfully outcompete AMD (and everyone else fighting for capacity at TSMC) they need to get their process technology back on track. 18A looks good according to rumors, but it only takes one short-sighted bean counter of a CEO to spin off fabs in favor of outsourcing to TSMC, and once that’s out of house it’s gone forever. Intel had an engineer-CEO in Gelsinger; they desperately need another, but my fear is that the board will choose to “go another direction” and pick some Welchian MBA ghoul who’ll progressively gut the enterprise to show quarterly gains.

rimshot

Science: knowledge workers stop being consistently productive past 40 hours per week, and probably less than that

Rentier-capitalists hot boxing their own farts recreationally: ackshually the problem is we let you dirty fucking peasants go home to sleep at all

I’ve got two big sycamores in my front yard, and they both are currently dropping leaves the size of dinner plates in enough quantity to completely cover large portions of the yard. If I don’t rake or mulch them, they will smother whatever ground cover that’s underneath them. I know this because I tried leaving them one year and it took the next three years to get all the mud pits left behind in the spring to fill back in.

Sorry. Not casting aspersions on you, just despairing at the situation.

Working on it, but for the overwhelming majority of people emigrating is a hell of a lot harder than just showing up in another country and saying “my place sucks, can I come in?”

The math leans towards the former, but when the two hypotheses suggested by the data are “we are actively and selectively targeting noncombatants” and “we just don’t give half a shit who we’re killing,” in a sane world you’d be universally branded as “the baddies” in the conflict.

On most carriers this is code for “coach, but it’s an exit row so we’ll charge extra for the legroom.”

In that case (as is the case with most games) the near-worst case scenario is that you are no worse off trusting Valve with the management of item data than you would be if it was in a public block chain. Why? Because those items are valueless outside the context of the commercial game they are used in. If Valve shuts down CS:GO tomorrow, owning your skins as a digital asset on a blockchain wouldn’t give you any more protection than the current status quo, because those skins are entirely dependent on the game itself to be used and viewed – it’d be akin to holding stock certificates for a company that’s already gone bankrupt and been liquidated: you have a token proving ownership of something that doesn’t exist anymore.

Sure, there’s the edge case that if your Steam account got nukes from orbit by Gaben himself along with all its purchase and trading history you could still cash out on your skin collection, Conversely, having Valve – which, early VAC-ban wonkiness notwithstanding, has proven itself to be a generally-trustworthy operator of a digital games storefront for a couple decades now – hold the master database means that if your account got hacked and your stuff shifted off the account to others for profit, it’s much easier for Valve support to simply unwind those transactions and return your items to you. Infamously, in the case of blockchain ledgers, reversing a fraudulent transaction often requires forking the blockchain.