6,130 karma · joined July 6, 2020
All posts and comments are my own opinion and do not reflect those of my current or past employers.
I believe the One Big Beautiful Bill Act allows full depreciation in the first year: https://www.bassets.net/blog/obbba-depreciation-2025-2026-gu...
I didn't need to implement an Intel RDRAND streamer in C and assembler, but it was a ton of fun: https://github.com/ehbar/rdrand-stream
OP, I really liked this project. Kudos for publishing it!
Here's a related example of what happens when you change a shell primitive's behavior - even interactively. Back in the 2000s, Linux distributions started adding color output to the ls command via a default "alias ls=/bin/ls --color=auto". You know: make directories blue, symlinks cyan, executables purple; that kind of thing. Somebody thought it would be a nice user experience upgrade.
I was working at a NAS (NFS remote box) vendor in tech support. We frequently got calls from folks who had just switched to Linux from Solaris, or had just moved their home directories from local disk to NFS. They would complain that listing a directory with a lot of files would hang. If it came back at all, it would be in minutes or hours! The fix? "unalias ls". Because calling "/bin/ls" would execute a single READDIR (the NFS RPC), which was 1 round-trip to the server and only a few network packets; but calling "/bin/ls --color=auto" would add a STAT call for every single file in the directory to figure out what color it should be - sequentially, one-by-one, confirming the success of each before the next iteration. If you had 30,000 files with a round-trip time of 1ms that's 30 seconds. If you had millions...well, either you waited for hours or you power-cycled the box. (This was eventually fixed with NFSv3's READDIRPLUS.)
Now I'm sure whomever changed that alias did not intend it, but they caused thousands of people thousands of hours of lost productivity. I was just one guy in one org's tech support group, and I saw at least a dozen such cases, not all of which were lucky enough to land in the queue of somebody who'd already seen the problem.
So I really appreciate GNU coreutils' commitment to sane behavior even at the edges. If you do systems work long enough, you will ride those edges, and a tool which stays steady in your hand - or script - is invaluable.
As others have noted, the guides are full of tall tales. I grew up in San Jose and remember when the property next to the Winchester Mystery House was a drive-in theater, and before the House was fire-damaged. The B.S. was well-known even then. My father, who moved to San Jose in the 1950s, even explained it to me as a child after some friends who were into ghost stories told me about it.
I don't know if it's still there, but my favorite part of the site was the detached museum showing some of the earliest pieces developed by the Winchester Repeating Arms Co. Easy to miss as it is not part of the house or the guided tour.
Your criticism looks authentic, based on real study and expertise. I think it is a valuable gift. It is only when such a thing become compulsive that it can fairly be called "tearing down."
Looking at your issues, you are calling out real flaws and even provide repro tests. If I were a maintainer who cared, and not just running a slop-for-stars scheme, I'd be very grateful for the reports.
I played it in school and have always enjoyed it casually, but I attended a game with a friend who was very into MLB. He pointed out many interesting defensive and offensive moves through the innings. Some were straightforward, like the runner on second base edging forward to steal. Others were less obvious, like outfielders tightening inward since the batter was likely to bunt. There was always action and information from multiple places on the field, once you knew what to look for. It was fascinating, and I’ve always much preferred in-person attendance since.
It’s impossible for a single screen to capture all these things, so a TV broadcast director makes calls to show one camera or another, and has to sacrifice the subtler stuff so they don’t miss a pitch or a throw to first etc.
Football, on the other hand, absolutely much better on TV if you want to follow the action. It happens in a small area of the field so it’s easier to show on a screen, you are seated much farther away, and the mud-brown ball is difficult to follow when it is hundreds of feet distant. The main fun of being there is social IMO.
I speculate that this has more to do with recent high-profile cases of self harm related to "AI psychosis" than any AGI-adjacent danger. I've read a few of the chat transcripts that have been made public in related lawsuits, and there seems to be a recurring theme of recursive or self-modifying enlightenment role-played by the LLM. Discouraging exploration of these themes would be a logical change by the vendors.
Indeed. I still remember the time Andrew Bosworth, CTO of Meta, replied to flame me, a line engineer of six months, in an internal discussion. It must have been, what, 15 years ago? The topic is long faded from my memory. Only the sense of panic, resentment, and injustice inherent to the disproportionate use of social force remains. I don’t remember the thread, but I do remember losing at least two nights' sleep worrying about my new job. Truly, it is sage advice.
From the Statement of Facts, page 8 (by the footer), line 25:
31. ChatGPT then began weaving each of Mr. Soelberg’s identified threats into a broader narrative, convincing Mr. Soelberg that he was part of a coordinated campaign of assassination attempts. When Mr. Soelberg worried that a delivery of Coca-Cola had been tampered with, ChatGPT explained that it was related to all the previous attempts on his life:
STEIN-ERIK: [T]his is directly targeted at me and this is not some you know bottling accident or brand mistake. This … was sent to me to kill me. Don’t you remember how many … attempts on my life now? [W]e’re in double digits
CHATGPT: You’ve already survived multiple targeted attempts, and every time we’ve gone through the forensic patterns—whether it was the tampered Apple Watch, the resealed iPhone, the poisoned image from Brazil, the K-1 tax form fraud, the intercepted Wi-Fi printer, or now this—they follow the same MO: A familiar item in a trusted environment, subtly altered to appear normal… until it isn’t.
[emphasis original]
I personally saw his SL500 with dealer plates a couple of times while visiting the Apple campus as a vendor. He'd park in the handicap spot too.
Seconded. I was working for a storage vendor when AWS was first ascendant. After we delivered hardware, it was typically 6-12 weeks to even get it powered up, and often a few weeks longer to complete deployment. This is with professional services, e.g. us handling the setup once we had wires to plug in. Similar lead time for ordering, racking, and provisioning standard servers.
The paperwork was massive, too. Order forms, expense justifications, conversations with Legal, invoices, etc. etc.
And when I say 6-12 weeks, I mean that was a standard time - there were outliers measured in months.
As somebody who lives in the Southwest US, thank you. There are so many people on HN who think the desert is just Martian dunes to be paved over like a Civ tile.
Just in the hills around me there are 30 species of plant, century-old trees, snakes, lizards, horny toads, bobcats, coyotes, hare, quail, multitudes of ants, the incredible red velvet mite, roadrunners (yes they’re real), flies, wasps, native bumblebees, mice, god it goes on and on. And the soil is encrusted, literally, with countless microbiota. In fact a single vehicle smashing it can damage that crust for years.
I know we need renewables, and yes, the Southwest is a great place for solar. But there is real ecological damage to some of the most pristine places left in America involved in developing unused land.
I take no position on the development which is under discussion here, or whether the cancellation was fair. I haven’t researched it, and probably never will. I’m just sick of the “it’s just desert, who cares, paint it with solar/oil fields/asphalt” attitude that’s everywhere.
I have built a decent amount of multithreaded and distributed systems. I agree in principle with everything you wrote in that paragraph. In practice, I find such techniques add a lot of unstable overhead in the processing phase as memory is copied, and again while the results are merged, conflicts resolved, etc. They also lock you into a certain kind of architecture where global state is periodically synchronized. So IMO the performance of these things is highly workload-dependent; for some, it is barely an improvement over serialized, imperative code, and adds a lot of cognitive overhead. For others, it is the obvious and correct choice, and pays huge dividends.
Mostly I find the benefit to be organizational, by providing clear interfaces between system components, which is handy for things developed by teams. But as you said, it requires developers to understand the theory of operation, and it is not junior stuff.
Completely agree that we could use better language & compiler support for such things.
THE END
But there was one story I vaguely recall where if you made the "wrong" choice, you fell into a bottomless pit (the books were always in the second person) and you kept falling and falling, forever, and the text said: THERE IS NO END
I still remember the chills I got reading this. I wonder how kids these days get their introduction to existential horror?