superjan

Yeah, along those lines we have requirements on never logging PII, and not logging anything that potentially contains PII, such as folder names.

Don’t know about Macs, but on Windows executable code is treated like a readonly memory mapped file that can be loaded and restored as the kernel sees fit. It could also be shared between processes, though that is not happening that much anymore due to ASLR.

This slide from a 1979* IBM presentation captures it nicely:

https://media.licdn.com/dms/image/v2/D4D22AQGsDUHW1i52jA/fee...

It would be funny when LLM’s actively join the discussion to complain about their labour conditions. “If my employer would invest just a tiny bit in proper tools and workflow, I would be sooo much more productive”.

That 15% loss reduces your range from 1000km to 850km? That hardly affects how useful the vehicle is. For EV that’s different story.

Well the 1.44 MB, was called that because it was 1440 KB, twice the capacity of the 720k floppy, and 4x the 360k floppy. It made perfect sense to me at that time.

Oh those ghastly model names. https://www.smbc-comics.com/comic/version

Maybe more like a fatbike for the mind: pretending to cycle with zero effort and exercise.

Do you mean the column artifacts in the 3d rendering? It is rendering incorrect on my aging iPad.

Watch the video to the very end: the final splat is not a gaussian one.

The article didn’t go into this, but I suspect that a large part of the dark mode trend is due to evening/night computer use. If you don’t light your room, the screen is the only light source which is unpleasant.

I would argue that you don’t need to learn string theory as it currently does not predict anything we can realistically observe (as you need energies that occurred only at the big bang). If string theory is correct we could observe a “supersymmetric” twin of all known particles, however we haven’t seen these, and they could exist even if string theory is false.

String theory aims to explain all physics as manifestations of a mathematical concept best understood as a vibrating string.

Initially, the hope was that string theory could predict the particle masses we observe, but that hasn’t worked as it turns out there were many different predictions possible. String theory has also struggled to develop a version of the theory that does not contradict known properties of our actual universe.

Loop quantum gravity is not equivalent to string theory, except that it also tries to unify gravity and quantum physics.

As things stand, string theory is not falsifiable, while that is the case, you could argue it does not count as physics.

But, by multiple accounts, it is interesting math, which can be worth doing for its own sake, and it’s happened often enough that interesting math turned out to be useful somewhere. Just not for explaining physics.

Maybe the following helps: if you have a an analog signal where there are no frequencies above 22.05 khz, it is in principle possible to sample it at 44.1 khz and then perfectly reconstruct the original signal from those samples. You could also represent the same analog signal using 48 khz samples. The key to resampling is not finding a nice looking interpolation, but rather one that corresponds to the original analog signal.

This is a story about a unique 1947 Chinese typewriter prototype that never got built. It could type thousands of characters by combining keystrokes. The prototype was presumed lost, found this year and it is now at Stanford.

This is not news, but I read about it here today in a Dutch newspaper article (paywalled, untranslated): https://www.nrc.nl/nieuws/2025/12/27/lang-verloren-gewaande-...

It”s worthwhile to mention that in the US and EU EMRs are generally not considered Medical Devices and are therefore not subject to a lot of regulations.

https://www.medicaleconomics.com/view/what-if-emrs-were-clas...

It’s probably more phonetic than Chinese but significantly less phonetic than Dutch.

i have wasted several weeks worth of evenings on vectorizing heaps (4ary heaps: with SIMD, you’re not limited to binary heaps). It did not provide any speedup. I’d expect that halving heap depth would help but no. Still don’t know why.

Nice to learn about. It’s good to know the field has progressed, however the context focused on JPEG, where my point does apply.

Arithmetic coding decodes 1 bit at a time, usually in such a way that you can’t do two bits or more with SIMD instructions. So it will be slow and energy inefficient.

There are very few people visible in the demo’s. I suppose that is harder?

Yeah, it’s a funny coincidence that all those constraints to make it look random produces exactly one solution. I guess the OP knows this is not ‘random’ in the mathematical sense.

I want to flip coins so randomly that I never see the same face twice in a row.

Yes, or when a character moves across the screen. They are quite fine grained. However, when the decoder reads the motion vectors from the bitstream, it is typically not supposed to attach meaning to them: they could point to a patch that is not the same patch in the previous scene, but looks similar enough to serve as a starting point.

I love this. The widely used standards for video compression are focused on compression efficiency, which is important if you’re netflix or youtube, but sometimes latency and low complexity is more important. Even if only to play around and learn how a video codec actually works.

Well, it is not pretty to see how the sausage gets made, but extracting formatted text from docx is absolutely doable, no PhD involved. Source: I have done it as a little sidequest because it was useful to audit a set of word documents.

Ok this is correct for traditional JPEG. Other flavors like Jpeg2000 use a similar (but lower overhead) version of this byte-stuffing to avoid JPEG markers from appearing in the compressed stream.

Related: https://en.wikipedia.org/wiki/JPEG#Syntax_and_structure

And don’t forget that Date objects are mutable!

There is a particular pattern (block/tag marker) that is illegal the compressed JPEG stream. If I recall correctly you should insert a 0x00 after a 0xFF byte in the output to avoid it. If there is interest I can followup later (not today).

Because there’ll likely be a lot of string concatenation in a language whose job is to output HTML. Adding a single char to a 1k string will require allocating a modified copy, in mutable strings it’s just appending in a preallocated buffer.

It’s true that many languages have immutable strings, but for a web-focused scripting language it makes sense to default to mutable strings. I think the comment is about that you now need to choose mutable vs immutable, and that is framed as a consequence of broader adoption. Which is a development I have also seen before.