made you look
It was Apple. Or rather, regulators and partnering companies leaning on Apple to manage the content on their app store better, including the content that you could find via those apps.
Could say something about how the app stores are a monopoly power, and the chilling effect these wide ranging and heavy handed content policies have, and why the open web (and web apps) are a better option. But we also handed the web over to Google anyway, so it’s not that much better.
We’re as close to quantum computers as we are to ChatGPT becoming sentient.
The calculator leaked 32GB of RAM, because the system has 32GB of RAM. Memory leaks are uncontrollable and expand to take the space they’re given, if you had 16MB of RAM in the system then that’s all it’d be able to take before crashing.
Abstractions can be super powerful, but you need an understanding of why you’re using the abstraction vs. what it’s abstracting. It feels like a lot of them are being used simply to check off a list of buzzwords.
And here, they are donating for a project by DHH, because they like the project
Said project is an Arch installer with some extra packages thrown in by default, not exactly groundbreaking stuff.
Ehh, bots have always presented nonsense UAs to servers. And since modern browsers hard-code the OS version in the UA string, pretending to be an old browser on an old OS could be a (probably ineffectual) way to bypass fingerprinting.
Anything that polls location data can record it and sell it, probably more apps that sell it than don’t.
Funny thing is, it was actually the device they connected that was faulty, the build of Windows they were using just didn’t handle that failure condition at the time.
MS at least learnt that lesson (for the most part), actually test things first.
You can turn the feature off entirely, or just not talk to people who post them? It’s not something like tiktok where you get pushed a bunch of random videos, it’s stuff that people you know are sending you.
He stores all his footage in full quality instead of just storing his final edited videos in a compressed format.
That’s the right way to do it, you want to avoid generation loss as much as possible.
Most likely an hardware issue, ZFS has seen similar types of corruption with certain drives under normal operation.
It was an issue for a long time that browsers just ignored the caching headers on content delivered over HTTPS, a baked in assumption that they must be private individual content. That’s not the case now, so sites have to specifically mark those pages as uncachable (I think Steam got hit by something like this not that long ago, a proxy was serving up other peoples user pages it had cached).
But for something like Google Fonts, the whole point of it was that a site could embed a large font family, and then every other visited site that also used it would simply share the first cached copy. Saving the bandwidth and amortizing the initial cost over the shared domains. Except now that no longer holds, instead of dividing the resources by the amount of sites using it, it’s multiplying it. So while a CDN might put the contents physical closer to the users, it doesn’t actually save any bandwidth (and depending on how it’s configured, it can actually slow page loads down)
Browsers partition the cache by “origin” now though, so while it can cache HTTPS content, it can’t effectively cache shared content (It’ll store multiple independent copies).
So Youtube still works fine, but Google Fonts is pointless now.
Edit: Oh yeah, and any form of shared JavaScript/CSS/etc. CDN is now also useless and should be avoided, but that’s always been the case.
Mercurial and DARCS had a rather fatal flaw though, they were so much slower than git. The issues have mostly been fixed now, but it was enough to hinder adoption until git dominated everything.
Git also has a rather big flaw, it’s “good enough”. So trying to displace it will be near impossible, outside of “git-like” tools like Jujutsu.
Ahh, yep it turns out ARM actually removed Thumb support with their 64-bit transition, so their instruction length is fixed now, and Thumb never made it into the M* SoCs.
one of problems with CISC is that it has variable length instructions
RISC systems also have variable length instructions, they’re just a bit stricter with the implementation that alleviates a lot of the issues (ARM instructions are always either 16-bits or 32-bits, while RISC-V is always a multiple of 16-bits and self-describing, similar to UTF-8)
Edit: Oh, and ARM further restricts instruction length based on a CPU flag, so you can’t mix and match at an instruction level. It’s always one or the other, or it’s invalid.
a nonprofit owned by a for profit company
It’s the other way around, the foundation owns the corporation.
Still feels like the corporation is the one making decisions though.
This is a problem that Nvidia is capable of solving but they haven’t been interested in it for over a decade so I don’t see them starting now.
They actually recently open sourced a bunch of required infrastructure, and hired a bunch of the OSS driver maintainers.
It’s all still pretty crap, but there’s more hope now.
Yeah “universal memory” is the holy grail, seemingly as hard to find as it as well.
The articles on Wikipedia about the related tech is great, it’ll mention something like “Developers expect commercialisation to happen relatively soon” and then link to an article from 2004, or research papers from the 1980s.
Shared memory is different to unified memory, AMD’s got an implementation of the later with their “Ryzen AI MAX+” (ugh) systems, does quite well in benchmarks.
It also doesn’t hurt that Apple puts the RAM on the SoC and gives it a truckload of bandwidth. DDR5 is about 70GB/s, meanwhile the M4 Max is around 540GB/s.
I’m still annoyed that “OPAQUE” never seemed to catch on. Uses a username/password combo as normal, but never actually sends the password to the server, only a proof of knowledge. Even if the server is hacked and the DB leaked the attackers can’t actually recover anything resembling a password from it, since the server simply never possesses it.
Passkeys are superior (No password at all), if only the UX around them was better.