Remember when Darl showed some “encrypted code” that he claimed was stolen and added to Linux and it was really just some POSIX definitions from a header file taken from BSD “encrypted” with a wing dings font? Those were some wild times.
Exit codes from processes are damage points that you take against your HP. When your HP runs out, the distro reformats itself to a clean state.
Just for the sake of comparison, Alphabet had $308 billion in revenue and $74 billion in profit in 2023 if I’m reading the numbers correctly. But they need cheaper labour.
Shake and bake in full effect.
Who’s ready to fly on a zipline?
Don’t forget the interactive video they did for an anniversary thing a few years back.
In the recent Musk biography it was said that at some point after a meeting with NASA he changed his laptop password to “ilovenasa” so you’re not far off in terms of terrible password security if the story is accurate.
Donald Knuth, author of The Art Of Computer Programming, basically our bible, famously doesn’t use email.
Maybe we’re already there and death is just the garbage collector freeing up more space.
Ironically, all of these things except Abrowser are based on Konqueror’s original engine, KHTML, so Konqueror was actually the OG engine. KHTML was forked to WebKit, which was forked to Blink, which became the underpinnings of Qt WebEngine, which Konqueror now uses.
This is also why KHTML still appears in the user agent strings for all of these engines, but back in the day the Gecko engine used in Mozilla products was already a thing and KHTML was the alternative to that, hence “KHTML, like Gecko”.
Many password managers like 1Password and Last Pass and KeePass and all the big ones can store MFA details nowadays.
Definitely Hamilton. Its nickname even sounds evil: The Hammer.
Bought a sweater I saw in an ad. Like a 70s style one, like it was the sweater that inspired both Tron and the Twister board game. Hasn’t arrived yet but I’m hopeful it isn’t complete trash.
Perl I believe is where the programming adage of TMTOWTDI comes from — There’s More Than One Way To Do It. Python was an anathema to that ideal, where TOOWTDI — There’s Only One Way To Do It, or at least one ideal way
I don’t know man, speaking as someone who lives in a hurricane-heavy locale we have to deal with broken windows due to storms with some regularity.
15 or so years ago I did a rough and dirty implementation of approximate addresses using the idea of just dividing street segments up by the address numbers on them and going from there. For instance, in the Canadian Road Network Files, they provide smallish segments of streets that usually line up to things like cross streets in metro areas, and they come with the ranges of the street numbers in the metadata, so you’d get something like a starting value of say 200 and and an ending value of 212 for a section of, say, Yonge St, and you could just divide that segment up across those values directly. You’d generally get within a few metres of the correct address. Close enough at the time for our use cases, at least. For more rural areas it didn’t work out so well, but for metro areas it was actually pretty decent. This could all be done via a single Postgres/PostGIS query with the right inputs and address parsing in front of it.
It wasn’t perfect and later came various APIs and whatnot for doing this sort of stuff, but it was pretty decent for such a relatively simple implementation.
It’s also been a known thing ever since the demo occurred. This isn’t news, it’s been a known thing for basically the last 15 years.
https://xkcd.com/538/