HNHacker News
TopNewBestAskShowJobs

27183

329 karma · joined July 3, 2026

submissionscomments
27183··on Changes at Google DeepMind: Demis Hassabis from CEO to Chair, Jeff Dean departs
"Hey Siri, find me gas stations along my route" routinely fails now. That worked great for years. Total clown show.
27183··on Civilian plane crash in New Mexico tied to military GPS blocking
There's nothing inherently unsafe or unreliable about old airplanes. Aircraft maintenance and inspections are very rigorous and evidence based as compared with almost any other mechanical systems you might interact with. I flew a 1949 Piper PA-16 Clipper with a fairly anemic 108hp Lycoming O-235 with auto gas STC. I'd say it was every bit as safe as any other light single engine airplane, so long as you pay close attention when the wheels are touching ground and mind your density altitude.

In some sense it felt safer than the 172 because I could fly a higher, tighter pattern. It was easier to lose a bunch of altitude on final by putting it sideways in an aggressive slip. The 172's small rudder didn't let it get as sideways, so it was a little more constrained. The 172 did have functioning instruments and dual radios, not just a handheld. It also had flaps. I think it was probably 10-15yr newer? Still a relatively "old" airframe. I probably had 5x or more as many hours in the Clipper so all that could just be biased towards familiarity.

Point being, old plane does not mean unsafe plane. It's not like you're riding around in some rusted out hooptie in the sky. There are rigorous mandatory inspections and maintenance schedules for every single component, which results in mechanical failures being really rare even in aircraft that are nearly 100 years old.

None of that obviates the need to know what you're doing, of course. The pilot in command needs to have control of the plane. I'm pretty skeptical of systems that kind of try to smooth over that sharp edge, I can understand the altruistic motivation behind it, but there's likely a side effect of reducing the perceived risk. That's a problem, because it makes people complacent. So in terms of overall safety, it might not be a win? You're trading on average higher complacency and lower situational awareness for maybe some better outcomes in rare situations? Probably not the best trade.

27183··on Civilian plane crash in New Mexico tied to military GPS blocking
That stuff just seems awfully gimmicky to me. I'm glad it worked and saved some lives. I don't think I'd want that system in my plane, though. I just wouldn't be able to trust it.

But I also wouldn't want anything to do with the new glass cockpit stuff, way too easy to just lose all your instruments at once. I'll take properly maintained, independent mechanical or electromechanical systems over digital ones every time for things that actually need to work.

Digital systems always seem to accumulate tons of complexity ("features") rendering them extremely brittle. Until we can figure out how to stop doing that, I prefer to avoid depending too heavily on them for important stuff.

The Cirrus parachute system seems pretty simple and trustworthy, that approach feels more directionally correct. Not much more complex than an automotive airbag.

27183··on Civilian plane crash in New Mexico tied to military GPS blocking
When I was training 20yr ago we practiced stalls, spin recovery, simulated random engine-out scenarios.. do they not do that anymore?

I was pretty confident barring some catastrophic mechanical failure I could probably get it on the ground or into the water (or trees) in one piece. The big question remains though: what now? If you're knocked unconscious (likely--lap belt, big flat instrument panel at face height) then two things can happen:

(1) if in the water, you drown before you can get out.

(2) if you're on land, the fuel tank right underneath that instrument panel or the ones up in the wings might torch you before you can get out.

It's probably about right to compare the risk profile to motorcycle riding.

27183··on Civilian plane crash in New Mexico tied to military GPS blocking
I've been in this situation too. But I was trained for it and had a mental checklist to follow. I never had a GPS, though. It seems from the details of the article, which you rightly highlighted, that the pilots were using their GPS as a crutch and had no ability to fall back on basic dead reckoning. It seems they didn't know where they were. That's pretty inexcusable, like embarrassing even.

I don't fly anymore, but I see similar behaviors developing on the water. People who use chartplotters for navigation don't have a very good understanding of what's going on around them. If you're just interactively following a computed lay line or a plotted course you don't really need to know what the currents are doing. You don't need to know what the hazards are. You're not actively engaged in navigating the boat.

27183··on Civilian plane crash in New Mexico tied to military GPS blocking
> Heavy weather and an instrument approach or confounding factors? Not accurate imho.

Then what are you supposed to do when your GPS craps out on approach in low visibility and heavy weather?

Obviously the answer is "fly the airplane". Which means you look at your artificial horizon, set trim and power for max climb, get to a safe altitude and figure it out.

If you're paying attention you already have your chart folded to the airport you're landing at, so it shouldn't be too hard to orient yourself and figure out what's next. Either you'll be making another attempt at this airport without GPS or you'll be going somewhere else.

There's never an excuse for failing to fly the airplane. That's basic airmanship. You need to be able to do it regardless of whether your GPS is working.

27183··on Civilian plane crash in New Mexico tied to military GPS blocking
Dunning-Kruger lives!
27183··on Civilian plane crash in New Mexico tied to military GPS blocking
Systems fail for all kinds of reasons, if you're dependent on one SPOF without any backup, bad things will happen eventually. In aviation we're taught to think this way from the very beginning. Always have a spot picked out where you will attempt to land the airplane when (not if!) you lose your engine.

Even in the absence of GPS jamming, you can effectively lose GPS for all kinds of reasons in a plane--a connector failing somewhere on the back of your panel, a wire chafing through, etc. GPS is nice, but it's probably a lot less reliable in most light aircraft than the other options.

It's been 20yr since I've flown a plane, so maybe attitudes have changed, but my instructors always stressed the importance of always being able to fall back quickly and seamlessly to a paper chart, your watch, flight computer, and basic instruments. Because you will lose everything else at some point.

27183··on SQLite Critical CVEs or LLM Slop?
It'll have to be pretty much all the ways. One way will stick. The rest will be forgotten failures.
27183··on SQLite Critical CVEs or LLM Slop?
Yeah that sounds great! A company guillotine is absolutely something I could get behind. Problem is I don't think there's any way it could possibly happen politically. Whereas we have a really strong existence proof for e.g. the Professional Engineer certification and other professional coherence mechanisms. That seems to work, albeit not without its own inefficiencies. I doubt anyone, though, would advocate for some kind of laissez-faire situation where the profit incentive aligns with the regulatory one. Historically that hasn't gone well. A lot of people died.
27183··on LLMs reward expertise
It was a general purpose computer, just a small one. Anything you could do on a "real" computer could be done on a calculator, albeit with tighter constraints. It might help to have some higher math objective to accomplish, because that would better utilize the preloaded system software. But in terms of the hardware? Probably not super relevant.

I made a lot of use of the TI-89 era CAS in college. But IMO the TI-83 era manuals taught me more about both math and computers than the subsequent generations could have.

27183··on LLMs reward expertise
maybe outing myself as a dinosaur, but "back in my day" the calculator came with a book that detailed exactly how to use it. Both the high level basic language and the low level system language. Not knowing how to use it is simply a failure to Read The Fucking Manual.
27183··on Rear center fuel tank adds roughly 20k liters and extends range by 1k NM
> how else are you going to get there?

Sailing would be more fun, IMO. Might take a quarter or half a year though.

27183··on Rear center fuel tank adds roughly 20k liters and extends range by 1k NM
This is exactly what I was thinking of when I wrote it down ;)
27183··on SQLite Critical CVEs or LLM Slop?
> "For a plane to fly as well as a bird it has to be able to flap its wings".

> "For a submarine to swim as well as a fish it has to be as light as fish".

These are false equivalences. The post you're responding to defined intelligence as learning rate. LLMs unequivocally do not learn. You can disagree with OP or agree, but what you have done is out of bounds. You're implicitly claiming that LLMs learn, albeit differently from humans. This is categorically false, unless you count training as some kind of "learning".

That's of course absurd, almost no user of an LLM also trains it. Instead they rely on queries submitted to pre-trained LLMs ("inference"). And don't bother yapping about context windows, it's just not anything like learning.

27183··on SQLite Critical CVEs or LLM Slop?
100%. I don't think "AI" has changed anything wrt to the responsibility of the tech industry in general. Tech has always been pretty much devoid of ethics or a sense of responsibility at the executive level (and therefore "management" more broadly). But before LLMs it was easier for ethical engineers to surreptitiously steer things towards responsible implementations. I suspect also competence correlates pretty strongly with intellectual honesty--narcissists and other personality defectives generally aren't terribly capable of the kind of introspection necessary to learn deeply. With the deluge of LLM slop, it's much harder for even a responsible manager to differentiate the competent from the incompetent, and now the dishonest, unethical folks have more leverage.

So now the problem is highly visible. There's only one solution I can think of, and that's to hold individuals (not corporations) responsible for professional malfeasance.

27183··on Rear center fuel tank adds roughly 20k liters and extends range by 1k NM
You could pack a lot more in if you sedate them and put them in racks like they have at the morgue. TBH I'd sign up for that on a long flight if the sedative recovery wasn't bad.
27183··on RipGrep musl binaries occasionally segfault during very-large searches
Yeah in that case just closing it and moving on would be better IMO. A sufficiently large fraction of the time the issues with vibeslopped code and/or analysis are bad enough once you start digging into it that it's not worth spending time on. My heuristic would be to simply ignore contributions derived from lazy prompts. I don't think there are very many healthy babies in that bath water.

So having the prompt available would be useful even in the degenerate case.

27183··on RipGrep musl binaries occasionally segfault during very-large searches
> What will you do when the prompt was "Figure out the bug and write a report for me".

The rational choice would be to cut your losses and stop reading at that point. Once you realize zero effort went into the prompt, there's no longer any reason to read the output. The age old truism still applies: garbage in, garbage out.

If you think it's worthwhile, close the issue with a comment: "please rework this and show your work next time". Otherwise just close it without commenting and move on.

27183··on RipGrep musl binaries occasionally segfault during very-large searches
Exactly, it would be so much better if they shared the prompts instead of the output, at least then we'd be able to make some sense of what they were thinking about.
27183··on The Beam Engine
High performance "modern" steam engines are fascinating, they're not necessarily simpler than their internal combustion successors, just different. Monotube boilers create superheated steam that pushes 1200°F, which is right around the same temperature as the exhaust gasses in truck's diesel engine pulling a large hill at maximum power. Hot enough to melt aluminum save for the presence of oil jets to cool the piston and a jacket of cooling water surrounding the cylinder. However, since there's no combustion happening in the cylinder of a steam engine, you don't have any cooling water surrounding it--that would be totally counterproductive. So steam engines operate in a thermal regime that is far more extreme than internal combustion engines. Consequently, bores are often cut slightly tapered to account for the temperature gradient across the stroke, in a double acting engine the cylinder bore has a slight hourglass shape, otherwise the thermal expansion would cause the piston to bind at the ends.

For a fun rabbit hole to dive down, check out Doble steam car technology or the Besler airplane engine.

27183··on Incremental – A library for incremental computations
Wow thanks for the link. My first reaction was "that's the jankiest thing I've ever heard of" but on reflection the author is correct about it being a fairly optimally fit predator. When the benchmark is .xlsx files on a shared drive things are bound to get pretty weird.
27183··on Oracle could face $7B collateral bill for Wisconsin data centre
From my limited second-hand understanding of orcl, a team that operates in a smooth and well greased manner is quite the anomaly. I could see why the company would have an immune response to it.
27183··on AWS: Inaccurate Estimated Billing Data – $1.7 billion
Yeah, negative tests are more important than the "test your tests" thing. Negative tests are themselves regression tests. Testing that a test works is something you do at dev time, it doesn't really live in CI. Negative tests, as well as positive tests, establish invariants on the code under test. They're effectively permanent, immortalized in the CI suite. Testing that the test actually works is a one time thing at the time the test is written. Permute the code under test, check that the test fails in the expected way, done.

You just have to trust your colleagues won't edit the tests in such a way that vandalizes the invariant. That's why you can never trust an LLM to edit a test. They're notorious for tweaking tests such that they pass.

27183··on Kaiser nurses say AI, surveillance are making their jobs and patient care worse
All of those beliefs seem approximately equally regressive? What percentage of people think there's something non-physical that actually exists? I'd put them in the same padded cell as the rest of those clowns.
27183··on Kaiser nurses say AI, workplace surveillance are making their jobs, care worse
https://www.youtube.com/watch?v=DpQamTrynBY

[edit] preemptively, if you're going to claim "but this isn't art so irrelevant" then I claim bull fucking shit. It's the same problem no matter how you slice it whether it be engineering, support, art, or medicine. Get real. Look inward. Touch grass. If you think AI is a good thing for your profession--whatever that profession might be--you're probably a delusional psychotic. It's OK, you'll thank me later.

27183··on Topcoat: The full full-stack framework for Rust
Is the name a POR-15 product reference? Incredible if so :D

  \m/_(>.<)_\m/
27183··on AWS: Inaccurate Estimated Billing Data – $1.7 billion
Yeah types and APIs that are difficult to misuse are way better than any regression test, canary, or what have you. Systems that are correct by construction always beat "you're holding it wrong".
27183··on First atmosphere found on Earth-like planet in habitable zone of distant star
A more cautious civilization might take measures to prevent emissions. There's potentially great value in remaining unnoticed.
27183··on AWS: Inaccurate Estimated Billing Data – $1.7 billion
I'm not quite following your objection.. I'd expect a test that checks the multiplier is correct would detect orders of magnitude discrepancy. So if you're billing $x/byte you'd write a test for the billing thing that checks that, given y bytes, the bill is x*y.

[edit] This may need to be an integration test to be effective, there is a certain peril to mocking that could bite you here. But that's fine, we have the technology.

← PreviousPage 6 of 10Next →