dmpk2k
dmpk2k on Hacker News
We have finite time in our lives. I'd argue it's eminently reasonable to spend time on things other that Emacs' guts, unless that's what tickles your interest.
What concrete evidence do you have that this crash, or the one earlier this year, was caused by the Russians?
You must have an incredibly high P(h)...
This is what American discourse has devolved to. "I saw the other side saying it!"
You're just proving my point without realizing it. I'm not even American, and have no horse in your race.
Lawfare has been an increasing problem for several administrations now. Like the parent poster says, each side is largely blind to their own abuses, but they're still abuses.
And then the other side uses it as justification to escalate further.
Hyperbole and trappings aside, that describes all mixed-market economies. And all major states have champion industries.
A few years ago I seriously contemplated making a game using software rendering, in part because the only target was SDL. I actually got a 3D engine running 2K@60Hz with HL2-level scenes, with the CPU basically idle, so it's not a terrible idea.
(Then LLMs started taking off and I decided I needed to reskill out of the industry, just in case)
That quote about Shadow Warrior doesn't pass the smell test. You're right there must be bottlenecks in the way.
The Build engine's rendering was stunningly simple (and dare I say: elegant). You could run hundreds of instances of Shadow Warrior on a single EPYC (since they mentioned Xeon) at that resolution and framerate if you rewrote the engine with modern mechanical sympathy in mind. On a modern desktop CPU it'd probably be over a hundred instances.
People, including many programmers, just don't grasp how much power we have under the hood nowadays...
Edit: my old iPhone SE, fully utilized, can produce the same GFLOPS as the Cray T3E (the one with thousands of DEC Alphas inside). This is our reality.
That was two decades ago. Things have changed a lot since then.
An official update hard (and permanently) bricked my S8 phone back when it was still the flagship. Samsung refused to fix or replace it because I had moved overseas meanwhile.
While "technically" valid, this never happened with iPhones despite frequent travels.
Don't buy Samsung consumer devices.
Likewise. I'm only interested in books that were either published before 2024, or are by authors I respect (e.g. Patterson & Hennessy), or by respectable academic publishers (e.g. Cambridge University Press). I used not to be so picky.
It also presents a bit of chicken & egg for new authors: nobody knows them, and now few will risk it, so they stay unknown. They must pursue other avenues to gain traction; far more than was needed a few years ago.
The deluge of AI books on Amazon has really been quite amazing. Between them and the higher risk of poorly-printed books, I don't buy from Amazon anymore. Now it's always direct from publishers.
It's a JIT nowadays. Admittedly an extremely simple one, to minimize compile times and maintenance overhead.
You can get substantial performance improvements by using guards though. See what Wings3D does with is_float() everywhere in hot numeric-heavy code.
Maybe it's just a regional thing, but it's showing 78 euros for the paperback for me. Plus I bought the paperback recently at that price too.
You're right, and yet it's also true that existing institutions have ossified. There is immense inertia.
You're right that a lot of material really does require a physical book. Anything even remotely technical.
That said, I would argue that a voice actor is far more significant than page formatting when it comes to novels. A good voice actor can turn a good story great, and sometimes a poor story to... acceptable.
I've read thousands of novels over the decades, both with and without audio, so I'm reasonably confident about the above.
The same Oman Trump was recently threatening to blow up? Heh.
It's weird for physicists to complain about nuclear weapons. They did it. Own it.
For all its faults, you won’t get a rug-pull like this with OSS CAD Suite and something like the ECP5, especially as a hobbyist.
Embedded developers often suffer under archaic toolchains. There's plenty of reasons for that, but one of them is UB: a newer version of the compiler can completely change an embedded program's behaviour.
I find your emotional language truly quite fascinating. I've heard people talk like that about drugs.
While true (beyond 30-50km/h), that assumes that cars are driving at a steady state. Obviously, cities with much more stop-and-go require more revving of engines.
Acoustic tyres are also gradually becoming the norm, primarily with EVs. This cuts noise by several decibels.
So it's not an unreasonable claim per se.
> There's essentially no reason to prefer the aligned load/store commands over the unaligned ones - if the actual pointer is unaligned it will function correctly at half the throughput
Getting a fault instead of half the performance is actually a really good reason to prefer aligned load/store. To be fair, you're talking about a compiler here, but I never understood why people use the unaligned intrinsics...
The only decent Prolog book out there, IMNSHO, is "Clause and Effect" by Clocksin. Maybe some of the later chapters might help?
All the other books that I looked at were pretty awful, including the usual recommendations.
You're probably aware of it, but if not: Uiua is much easier to understand in this regard.
They added arenas to SBCL recently. SBCL has a moving GC, and the Common Lisp spec was finalized in the 1990s.
Okay, this is just Lisp being Lisp, but it's still an example...
I suppose there are worse things than my scribblings sounding like a late-night kitchen gizmo ad. :)
Similar with Babylon 5, although the CG has not aged as well.