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.)
"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.
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?
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.
- 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.
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?
My book, The newline Guide to Bash Scripting: https://www.newline.co/courses/newline-guide-to-bash-scripting
[ my public key: https://keybase.io/l0b0; my proof: https://keybase.io/l0b0/sigs/-sU_dPlI9HzZthatZd5JCO9gZLIX2_pvhEeNmJDCjLQ ]