l0b0

Looking at articles about the surrounding area while being a passenger is a great way to discover future destinations, and to just learn what's out there. OSMAnd makes this really easy by toggling the Wikipedia overlay.

It does, actually! Because only the package definitions are needed, and you can get those from the tarball of the relevant nixpkgs repo commit. And since building+installing is the same Nix command as downloading+installing, whether the binary caches still have the old package (or are even still up) is only the difference between a fast download and a slower build. This is different from most package managers, where trying to install anything old means spinning up a complex build environment and learning a bunch of new tools.

Of course, if even the original sources are no longer available, you'd have to change the broken URLs. And if the source has somehow been scrubbed from the Internet you're SOL

You should try some good homemade lutefisk. No, not just lutefisk, that's like judging burgers by only eating the patty. Rather with all the accoutrements: fried bacon, pea stew, boiled cherry potatoes, and white sauce.

"GOG GALAXY is a long-lived product with a large and complex C++ codebase." Also known as a shitshow. Hopefully the new engineer(s) will be encouraged to at least add some tests and refactor things to stay sane.

No mention of a license, though. I guess it'll stay closed source.

Maybe it's time for some decently funded other organisation (not a teracorp) to take over Firefox specifically, then let Mozilla go its own way into the sunset. No idea how that could be arranged, though.

Just about every week I find "new" GitLab bugs which, after a quick search, turn out to be 5+ years old, with lots of community engagement, but seemingly zero movement from GitLab itself. I wonder what GitLab devs actually work on, because none of the new features in the last couple of years seem as impactful as fixing one of those bugs would be. (I still prefer it to GitHub, especially the CI model.)

Pinboard (still decent, just don't expect your money back if you pay for the permanently broken PDF export feature) until I can self-host Linkding[1].

[1] https://github.com/NixOS/nixpkgs/pulls?q=is%3Aopen+is%3Apr+l...

"May shrink on first washing" or something like it seems to be pretty common; you might've accidentally tried something on which had that labelling (or didn't, which would suck).

No mention of value engineering? Isn't that what every big company does to a successful product? Barely-noticeable quality decreases compound over years, and more noticeable ones are rationalized away as necessary for survival. It doesn't take a genius to see where that leads.

Also enshittification, the more general trend where an initial offering is excellent, maybe even provided at a loss, to spread the word and provide great feedback, and then more and more money is squeezed out of it while riding consumer satisfaction lag, until the offering is taken behind the shed and mercy killed.

It's happening now, not in 950 years.

It's mostly just semantic drift. "REST" is less of a mouthful than "JSON over HTTP". Nobody ever realised the potential of discoverability.

"Not only is there no reward, nor can you ever expect a reward, for doing the right thing, it also often comes at a personal cost."

That's too cynical. I take personal satisfaction in not taking such jobs, and that's no small award.

Absolutely, although it never got as far as an actual job offer before the rejection. A couple of minutes of online searches should be enough to highlight any horrible behaviour before even applying.

Nice find! As for the provider, since they missed this extremely basic step (don't trust the client!!) I would expect they have many more undiscovered vulnerabilities.

Thanks for the explanation, although I now have more questions :

- Why the "graph" aspect of "e-graphs", when it seems all of the ones I've seen in your article and on Wikipedia have only a single edge? Why not just "equivalences"?

- The Wikipedia page doesn't seem to explain the actual data structure. If it's a data structure, how is the actual data laid out in a series of bits? Or is "data structure" on that page used in a way which is meant to make sense to mathematicians rather than computer scientists?

- How does this relate to existing refactoring tools? Is this a new approach? Or is it what IDEs and language servers already use?

What is the context? Is there tooling to use these to simplify programs? Are they meant only for formal verification? Something else?