People of France: Your long national nightmare is over. I hereby gift you words for 70, 80, and 90:
Septante
Huitante
Neuvante
You are welcome. You can put my statue in the courtyard of the Académie Française.
Although to be fair when I think about Twitter discourse it feels like React has been around for about 100 years.
If your #github project uses #stalebot you are being actively hostile to your community and should stop it.
I'm looking at you, #esphome, and the 4 (at least!) identical bugs indicating problems with esp_touch that were all closed by stalebot. Some of them were reproduced and started discussion and debugging before being closed.
Auto-closing is for #support requests, not #bug reports. Bugs don't magically disappear just because you ignore them.
i'm not against cheap sketchy solutions to stuff.
"okay, this is shit, but it was obvious that it was, and i'm on a budget, so i'll settle for the shit solution since that's all i can manage for the moment."
what's less acceptable for me is when there's no warning. "hey, this sounds like a bargain" and then it turns out it was just 3 sketchy solutions in a trench coat.
it's a dick move on the part of HDD manufacturers to sell SMR drives without writing in big fat bold letters on them that they're the trashy option.
so
normal hard drives are now known as CMR (Conventional Magnetic Recording) drives. they had to retrospectively invent a name for them, now that there's a worse option in town.
these new ones are SMR (Shingled Magnetic Recording).
so, on a normal hard drive, data is stored a bit like on a vinyl record, on parallel tracks.
what SMR does is actually to put these tracks a little bit too close together. normally, this would ruin the data on the next track over, but the way they fix it is to compensate. turns out you can pack them closer together if you make sure to counteract the magnetic flux in JUST the right way.
but you HAVE to write out several tracks as a group to do this. and this group is called a zone.
unlike regular drives, where you can write out a single sector of 4 kB, on these drives, you're looking at writing out 256 MB or more if you're only changing a single sector of data.
if you're writing out big files, this is fine, but performance for small random writes is going to be horrible. the technique relies heavily on caching and writing out later to work properly.
so they're not very good, *especially* not for things like NAS or DB servers, where you *really* want stuff to be written to disk immediately for the sake of data integrity.
If you are an implementor of #ActivityPub, or any related social web apps or protocols, please try to come to the meeting on the future of ActivityPub standardization and related subjects next Wednesday, March 29. It's on-line and hosted by #FediForum and the W3C's Social Web Interest Community Group.
We want to hear from you! Standards should not be created in a vacuum. If you have tried to use ActivityPub (successfully or not!), tell us what you need! And perhaps get involved making it so.
TIL the .zip format is ambiguos enough that different parsers can see different files
Bug 1534483 - Ambiguous zip parsing allows hiding add-on files from linter and reviewers
https://bugzilla.mozilla.org/show_bug.cgi?id=1534483
the dirtiest secret you find when reverse engineering games is how many implementations of String they have.
This one is at least 3, plus it uses some stl so there's probably an std::string somewhere
Software developer, open-source enthusiast, wannabe software architect. I like learning and comparing different technologies. Also general STEM nerd.