l0b0

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?

Thank you for sharing! I tried to see if I could replicate the result (unlikely, as I'm not a cosmologist, just a Python developer), but it's not possible:

- They don't share all the input data, including something called "`.FITRES` calibration files" which seem to be necessary - the first command, `python BuildPP.py`, fails because it can't find `Pantheon/calibration_files/FITOPT000_MUOPT000.FITRES`.

- Some code must be meant to be run with a different Python interpreter than the rest, because the syntax is not compatible with the only version mentioned in the project (see below).

The project also has some troublesome but not fatal flaws:

- No exact information about Python version. The only hint I could find was the mention of needing Python 2.7 (two years EOL when the repo was created).

- No information at all about dependency versions. The project needs matplotlib, numpy, pandas, and pymultinest, but there's nothing about which versions of any of these were used for the analysis.

How would Swiss Re get the data except by collaborating with Waymo?

Great idea! Some feedback:

- The 24 hour horizon means you could get away without namespace functionality like categories entirely, especially when self-hosting for a small-to-medium-sized group.

- It's tiring to read sites with all monospace fonts. I can see how it might be useful if most posts contain a lot of code, though.

- Do you expect this to be open sourced?

The page returns HTTP 404, but I can't find a mention of a redaction. Embarrassment? Legal pressure? Or do they remove recent videos as a matter of course?

nixpkgs PR: https://github.com/NixOS/nixpkgs/pull/368404

Tiny nit: most of the units were good (s, g, M, R), but it seems a bit odd to use cm rather than m, and and GeV rather than eV on log scales.

No mention of usability/accessibility in the interior/architecture section, and barely a mention of regulation and cost. But it's expensive and difficult to come up with an interior/architecture which is user friendly and accessible, while conforming to regulations written in blood. So of course people with finite money are going to copy and paste existing designs. Doorways, corridors, corners, inclines, bathrooms, etc safe and fit for small children, the elderly, the visually impaired, people in wheelchairs, and so on. Items positioned so that inhabitants/users/visitors/customers can use their intuition to navigate the space, rather than having to ask someone all the time. It should be expected and natural to reuse.

On a related note, I suspect a lot of people these days assume that most "alternative" things are unusual for the sake of being unusual, and not actually some stroke of genius. Not saying they are always right, but there's certainly a lot of alt-crap out there.

Not sure why you're being downvoted - it's tautological that implementing the average opinion is going to end up with something average.

> 3. If the situation is so bad, why aren't companies training their staff directly, on the job?

Short-term and wrong-headed thinking. Most places seem to consider all employees basically "fully trained", and bizarrely treat on-the-job training as a favour to the employee. This is probably connected (influencing, influenced by, or both, who knows) to how tech workers have short stints at each company.

GitLab is better in some ways, worse in others. One thing GitLab is much better at is supporting a rebase strategies, making for a much nicer history. GitHub still doesn't know how to show the difference between the original version and a force-pushed one when reviewing, but that just works on GitLab.

Another good thing about GitLab is that all the CI code is right there, not in a bunch of separate repos. You can reproduce it locally pretty easily.

The main thing GitLab is worse at is refreshing the UI when the underlying state changes, without having to refresh. They're getting better at it, but to be fair GitHub also has plenty of issues with this.

It's a catch-all in case any single service is badly configured. This often happens while people are fiddling around trying to configure a new service, which means they are at the most vulnerable.

> I heard Nix is a great way to build containers though.

It is, I'd recommend the fantastic https://www.youtube.com/watch?v=6Le0IbPRzOE to appreciate some major differences.

Last modified a year ago - is it still maintained?

That sounds like hundreds of hours of work.

Did Pinboard get bombed by HN?

> Error: Connection refused

Hopefully coming soon to your favourite distro: https://github.com/NixOS/nixpkgs/issues/341665 :)