

The ladybird devs are currently in the process of switching language again from Swift to Rust, using LLMs.
made you look


The ladybird devs are currently in the process of switching language again from Swift to Rust, using LLMs.
And also, JSON was intended as a data serialisation format, and it’s not like computers actually get value from the comments, they’re just wasted space.
People went on to use JSON for human readable configuration files, and instantly wanted to add comments, rather than reconsider their choice because the truth is that JSON isn’t a good configuration format.


This isn’t sending your packets anywhere but their closest datacenter, not sure I’d trust MS (Or rather, Cloudflare) with your porn rather than your ISP who you’re actually paying.


The original use case for this stuff was unencrypted HTTP with a public WiFi connection, in which case your ISP is the owners of whatever shop you’re in and yeah they could see everything.
If you’re at home or whatever it offers effectively no benefits, doesn’t “block trackers” or whatever nonsense like Nord claims, but I don’t think Microsoft ever claimed that it did.


IPFS has gateways though, so you can link to the latest version of a page which can be updated by the owner, or alternatively link to a specific revision of the page that is immutable and can’t be forged.


Seems like we need to switch to URLs that contain the SHA256 of the page they’re linking to, so we can tell if anything has changed since the link was created.
IPFS says hi


It’s the same person running all of them, so yeah it is.


No, Nokia do own a bunch of patents on it, I’m pretty sure they also created (and have patents on) the HEIF format used in HEIC/AVIF as well.
Edit: search results were failing me, but here’s a couple.
https://blogs.windows.com/devices/2013/03/18/h-265hevc-high-quality-video-at-half-the-bandwidth/ https://mspoweruser.com/nokia-details-its-contribution-to-h-265hevc-hints-at-integration-in-devices/
Some newer radiation hardened stuff is 10x larger than that, older gear even more so. But that just reduces the risk, not sure it’s possible to negate it entirely.
An easier way is to just include more CPUs as part of the system, run them in lockstep, then compare the results by majority rule. If 2/3 CPUs say one answer and the third says something else, you discard the result of the third and go with the other CPUs.