Systemd hate is about it consuming things, and doing things badly.
gens
joined 1 year ago
Originally it was about code. Split it into reusable functions, and such.
SyStEMd fans don't understand, per usual.
Lets say you use a variable named abcd in your function. And a variable named abcb in a for loop inside the same function. But because reasons you mistakenly use abcd inside that loop and modify the wrong variable, so that your code sometimes doesnt work properly.
It's to prevent mistakes like that.
A similar thing is to use const when the variable is not modified.
Unix domain sockets, shared memory (classic and/or over anonymous file descriptors), file system in userspace, the (ms) ini format.
Was going to sleep when i wrote that.
Uds, shm, fuse for ipc. Ini for configs.
https://mastodon.gamedev.place/@badlogic/111071396799790275
The internet has made real time collaborative price fixing possible.
FF7 and supreme commander were complex. And devs then didn't have the tools we have today, not to mention game engines (there were, but not like today). And ps3 was a pain to program for. And, and...
Afaik they became less efficient. Because we banned some gasses.
I was gonna go with the other guys sensible answer, but i like yours more.
Having a company behind software means you can pay to have your bugs fixed. Big distros want that stability for their corporate customers. It's no secret or anything. KDE has sponsors, but doesn't have a direct relationship with a huge contractor like RH. Same reasoning for systemd.
Politics, basically.
Learn to behave.
And as naturally high as men ? Probably not. (Hence the "floded")
Hmm. I can't find ehere i got that from, other then it being more general. https://cscie26.dce.harvard.edu/lectures/lect02/6_Extras/ch01s06.html
Either way the whole point is to write programs/code that can interoperate and be composed. SysD programs comunicate over an "implementation is the specification" protocol, so they might as well be one blob instead of separate programs.