I mean, yeah, I wrote it kind of humorously up there, but I do actually think state diagrams are a good idea and modelling the known error paths is part of real software engineering.
However, I’ve never been in a project where anyone knew nearly enough about what we’re supposed to build, to be able to draw a state diagram before we got started. We would rather do a refactoring halfway through and then we would design a state machine to fit the requirements…
One time, we were drawing a state diagram of how the core loop in our application should behave. So, you know, first you have the preparation state, then when that succeeds, you go to the getting-things-ready state, then into the actual doing-things state, then the result-reporting state and so on. So, there was exactly one happy path.
Then we figured, we should also diagram all the error scenarios. If an error occurs in the preparation state, we should transition to the result-reporting state. But if an error occurs in the getting-things-ready state, we’ll need to go to an intermediate cleanup state before we go to the result-reporting state, and so on.
As we added more and more error paths, the arrows had to curve more and more, until the whole diagram eventually looked like an onion. That’s when I knew, we were doing real software engineering. 🙃
I always recommend these tutorials to folks for learning about ownership, as they offer a very visual explanation: http://intorust.com/
You can skip the first two chapters.
Reminds me of how frequently folks get color blending wrong (using linear blending results in darker colors). Or also volume sliders (using a linear scale results in much stronger volume changes near supposedly-silent volumes).
It just looks/sounds vaguely right and then no one ever questions it…
Oh wow, did they maybe search for someone with skills of a “server” and the Indeed algorithm soup got that mixed together with skills in server technologies…?
I know that QMMP has a built-in visualizer, and the webpage says that the visualizer is call projectM, which you can apparently also run standalone: https://github.com/projectM-visualizer/projectm
I would be surprised, if you couldn’t also sell an account with a bunch of stars on the black market to bot farm operators…
It won’t rise much beyond that, since you only get one update per package. Whether it’s upgrading Firefox from version 120 to 121 or to version 130, it doesn’t change much in terms of download size, nor the number of updates.
At least, I assume, Arch doesn’t do differential updates. On some of the slower-moving distributions, they only make you download the actual changes to the files within the packages. In that case, jumping to 121 vs. 130 would make more of a difference.
If you do want lots of package updates, you need lots of packages. The texlive-full package is always a fun one in that regard…
There’s Endless OS, which goes in that sort of direction. It includes even a good chunk of Wikipedia, so you can just install it on PCs and ship those PCs into regions where they don’t have internet.
Interesting, I always assumed they would be using a pretty optimal algorithm with their .tar.bz2 format, because they obviously benefit quite a bit from smaller downloads. Good to know that .tar.xz is actually better.
I think, you’ve answered your own question? There’s a lot of different formats for Linux. Getting them all correct and working on the different distributions is significantly trickier than just bundling a self-contained archive.
Having said that, they do actually provide a DEB repo since a few months ago: https://support.mozilla.org/en-US/kb/install-firefox-linux#w_install-firefox-deb-package-for-debian-based-distributions-recommended
I’m currently struggling with making a const API, so this really feels like the language designers heard my pleas. 🙃
Implementation of the add() function is here: https://github.com/raldone01/python_lessons_py/blob/main/lib.py
Ah yes, multiphonics.
On what operating system are you?
On Android, there should be a setting for it.
On a desktop OS, you can probably add
--private-windowas an argument into the launcher.Don’t know what the situation is on iOS…