> unlike anything we've seen before

They probably haven't seen (to pull a number out of a hat) negative three billion percent growth before either…

Didn't Nadella come from the Azure side? In that sense it'd make sense that what they were doing would spread to the rest of the company.

If anything, it might unbreak things.

I have my browser set to request, in order, English, a different English, then a non-English language. Some sites (Android docs, Gitlab, F-Droid) will send me the non-English content; Google even preferentially does their AI translation thing instead of the original English.

Then for some web sites it won't matter and display the dominant language of the country that you're accessing from. My Firefox sends US English as the only preferred language, but a ton of US tech companies default to showing web sites in Japanese without a way to change it because I access them from Japan. It's pretty typical of American companies that don't understand localization and accessibility.

Most infuriating is when they do it based on GeoIP. So what I'm in Istanbul currently, I know maybe a dozen words in Turkish. But no, and also they insist on having broken language switchers.

Isn't 32bit counter 49 days? Assuming that one was counting milliseconds, at least.

Only remember that because that's the limit for Windows 95…

100ns intervals. My favorite part of that story is how long after Windows 95 was released before anybody discovered the bug.

That's because people actually powered off their computer after work/leisure sessions. Someone on an unlimited night dial-up could had discovered it well before "anybody" but it's not like there was a built-in function to actually send a crash report to Redmond.

https://i.sstatic.net/p9hUgGfg.png

Specifically, it's disabling remote start, rather than the actual heating.

It's quite possible to be creative while not contributing to society or whatnot.

A crappy sand castle from a eight-year old that will be torn down when the tide comes in is not really contributing to anything useful, but can be quite creative.

I never disputed the fact that shut-ins can be ‘creative’, but instead focused on ‘hotbed’. I would characterize artistic failures as being more ‘original’ and perhaps ‘creative’ than successes, but they still lack value (to anyone but the creator). Regardless, this seems pointlessly semantic.

That's only if you want to watch specific things; some people just turn it on for entertainment, and change channels to have a spin at the roulette wheel for something better.

Unfortunately you can't really statically link a GUI app.

Also, if you happened to have linked that image to a.out it wouldn't work if you're using a kernel from this year, but that's probably not the case ;)

> Unfortunately you can't really statically link a GUI app.

But is there any fundamental reason why not?

> Also, if you happened to have linked that image to a.out it wouldn't work if > you're using a kernel from this year, but that's probably not the case ;)

I assume you refer to the retirement of coff support (in favor of elf). I would argue that given how long this obsolete format was supported was actually quite impressive.

Is there a reason the users must see all of the historic data too? Why not just have a post-commit hook render the current HEAD to static files, into something like GitHub Pages?

That can be moved elsewhere / mirrored later if needed, of course. And the underlying data is still in git, just not actively used for the API calls.

It might also be interesting to look at what Linux distros do, like Debian (salsa), Fedora (Pagure), and openSUSE (OBS). They're good for this because their historic model is free mirrors hosted by unpaid people, so they don't have the compute resources.

I'm not OP but I'll guess .... lock files with old versions of libs in. The latest version of a library may be v2 but if most users are locked to v1.267.34 you need all the old versions too.

However a lot of the "data in git repositories" projects I see don't have any such need, and then ...

> Why not just have a post-commit hook render the current HEAD to static files, into something like GitHub Pages?

... is a good plan. Usually they make a nice static website with the data that's easy for humans to read though.

That makes the mistake of thinking they'll care. Most likely they'll just keep downloading the encrypted garbage and never notice.

> That makes the mistake of thinking they'll care. Most likely they'll just keep downloading the encrypted garbage and never notice.

Not going to happen. They aren't going to add encrypted garbage to their dataset.