Recursion makes it cheaper to run in the dev’s mind, but more expensive to run on the computer.
Maybe for a Haskell programmer, divide-and-conquer algorithms, or walking trees. But for everything else, I’m skeptical of it being easier to understand than a stack data structure and a loop.
In a single one-off program or something that’s already fast enough to not take more than a few seconds—yeah, the time is spent better elsewhere.
I did mention for a compiler, specifically, though. They’re CPU bottlenecked with a huge number of people or CI build agents waiting for it to run, which makes it a good candidate for squeezing extra performance out in places where it doesn’t impact maintainability. 0.02% here, 0.15% there, etc etc, and even a 1% total improvement is still a couple extra seconds of not sitting around and waiting per Jenkins build.
Also keep in mind that adding features or making large changes to a compiler is likely bottlenecked by bureaucracy and committee, so there’s not much else to do.
Not necessarily. It depends on what you’re optimizing, the impact of the optimizations, the code complexity tradeoffs, and what your goal is.
Optimizing many tiny pieces of a compiler by 0.02% each? It adds up.
Optimizing a function called in an O(n2) algorithm by 0.02%? That will be a lot more beneficial than optimizing a function called only once.
Optimizing some high-level function by dropping into hand-written assembly? No. Just no.
Yeah, you have to be pretty deranged to mix multithreading and recursion together.
Error: undefined reference ‘money’
100%. Whatever Intel does at this point, I don’t trust it to be a fix so much as a mitigation or attempt to delay the inevitable until a few years after the warranty period.
If it’s possible for people to return their 13th/14th gen processor and trade up for a 12th gen, that would be the safest solution.
Moore’s Law is Dead shared an interesting video yesterday about these chips. Supposedly, leaks from his sources at Intel say that high voltages being pushed through the ring bus cause degradation. The leaks claim it shares the same power rail as the P and E cores, meaning it’s influenced by the voltage requested by the cores.
For context, the ring bus is responsible for communication between cores, peripherals, and the platform. This includes memory accesses, which means that if the ring bus fails and does something incorrectly, it could appear normal but result in errors far down the line.
Going beyond the video specifically, and considering what others have suggested as workarounds, it seems like ring bus degradation might be a decent candidate for the actual root cause of these issues.
Some observations around chips degrading were:
Some of the suggestions to work around the issue were:
All of those can be related to stress being put on the ring bus:
I’m not claiming anything definitive, but I think my money is on this one.
In some encoding scheme, those digits can represent something other than binary digits. If we consider your string of digits to truly be infinite, some substring somewhere will be meaningful.
Ok, what kind of monster names their executables .elf?
They certainly tried with Secure Boot. Thank Stallman that UEFI is a somewhat-open architecture.
Type-safe lipstick :)
To offer a differing opinion, why is null helpful at all?
If you have data that may be empty, it’s better to explicitly represent that possibility with an Optional<T> generic type. This makes the API more clear, and if implicit null isn’t allowed by the language, prevents someone from passing null where a value is expected.
Or if it’s uninitialized, the data can be stored as Partial<T>, where all the fields are Optional<U>. If the type system was nominal, it would ensure that the uninitialized or partially-initialized type can’t be accidentally used where T is expected since Partial<T> != T. When the object is finally ready, have a function to convert it from Partial<T> into T.
Smoldering at best, sadly. It will take a lot more before Reddit goes and Digg V3’s itself.
Every bit counts at least.
To be fair to PDFs, they can contain JavaScript. Blame Adobe for that and their originally-exclusive-to-Acrobat extension for that.
If he had said “LaTeX” or “roff”, that might have been a good example of something that blurs the line between the two. They aren’t specifically intended to be programming languages, but with a powerful enough macro system, a markup or typesetting language can be used in the same way as something like Brainfuck.
Nuzu also shut down within a day.
I don’t remember what it said exactly, but here’s a rough description:
It’s the King of the Hill if those kids could read they’d be very upset meme, with the piece of paper saying “JPEG XL memes” and the kids in the classroom being labeled “Android users”.
As an Android user, OP’s image was accurate.
.jxl still didn’t help.I gave up and grabbed a JPEG XL viewer/converter just to see it.
TCP is also deciding to ramp up the amount of boxes you kick over until the post worker gets crushed by boxes, at which point you decide to lower your box-kicking rate by half and try again.
NaN != NaN