As the saying goes, there’s only two hard problems in IT:
Caching, naming things, and off by one errors.
As the saying goes, there’s only two hard problems in IT:
Caching, naming things, and off by one errors.
Honestly, having a declarative package manager is pretty important.
Consider the following: We’ve had the transition from Sys V Init to Systemd recently. But what does it actually mean?
It means, that instead of running a command to start a service, you now flip a switch in a clear, standardized way. The advantage is that you can get a table-like overview over all the services that are currently running. You get an overview, in other words. That is worth a lot because it brings structure and clarity into your system.
Now, with package management it’s the same way. Instead of running a command to install a package, we should instead give a list of all the packages that we want to have installed, and the package manager should take care of making sure that they are installed. That would improve clarity, because you get a list of all the packages that are installed. It might also increase efficiency if you’re installing many packages, because large parts of the work can be done in parallel. And importantly, you get reproducibility. Imagine you just have a file where it names all the packages that should be installed. You can just take that list and copy it to another machine. Now you’ve cloned your package installations. I guess things like Docker, with their docker files, are kinda already going in that direction. But it would be nice to have support for it in the mainline operating systems.
you’re on a highway to hell.
I agree with you especially on the definition order of functions. I, too, define main()
first.
let the chaos reign
“We’re pushing the can down the road. Problem is, we’re running out of road.”
My father. He’s just a fine dude. Does a lot of things right, is never angry at anybody for too long, and just generally understands what’s important in life and why.
How to write spaghetti code:
I think that we have a perception bias towards things that interest us.
Since the elements in the top-right corner (C, O, N, P, S, Si, Fe, Al, Na, …) are interesting to us, that’s what we typically look at. And in that region, things are fairly balanced. It’s only in the regions where we don’t typically look, where we said “let’s just make it all metal so the categorization is done, call it a day, and move on”. I think.
Yeah, it’s also very difficult for me to focus on something if I don’t know where I’m going.
IMO the best knowledge comes from doing practical examples that actually interest you. I wouldn’t rush that.
I honestly started out not liking systemd at all, mostly due to the reports that it did waaay to much, but nowadays, I like the concept.
It is basically officially moving daemon management from a script-based approach to a table/database-based approach. That improves static analyzability, therefore increasing clarity, and probably even performance.
I agree that we should abandon scripts and move towards declarative software management, and abandoning sudo
for a more declarative system seems like a good step to me.
Yeah, good to know. today I learned …
GIMP feels non-intuitive sometimes.
For example, layers.
I expect that GIMP internally has a list of all objects that I added to the file. Like, text, brush drawings, pasted images. Instead, I cannot find that list anywhere.
If you have no money, and throw away all of it, you still have no money.
Yes they are. Capitalism brain-rot has infected most of US workforce today.
Two plates of rice or noodles with vegetables and salmon. Delicious. Actually, highest ROI that you could possibly hope to achieve in the universe.