Mine is that the useState hook is an actual plague on the entire React ecosystem. Regardless of your opinions of React, if you wanna use something then use it right.
Mine is that the useState hook is an actual plague on the entire React ecosystem. Regardless of your opinions of React, if you wanna use something then use it right.
systemd does a lot of things very right and a mayor reason that linux is in a way better place than 15 years ago. 27 unmaintained tools are not better than one that is professionally developed.
systemd has me in two places. Like, on one side, it’s just SO much better and easier than the rest - at least to me, someone who doesn’t work in IT and just wants his stuff to work. On the other, init freedom is essential, and we need the alternatives to stay alive.
APIs generally don’t need many alternatives, only implementations do. There’s no reason devs should be trying to provide init files in multiple formats. If the systemd team actually did something bad, then people could just make a different implementation of systemd without requiring a different format for init files. Arguing for more init systems is like saying we need more APIs to compete with both Wayland and X11, instead of just talking about implementations of those protocols.
Systemd solves a very important problem that was defined extremely well.
It also solves it badly, and solved a whole lot of other badly defined problems that it shouldn’t.
This is my argument. Do init. Don’t pull in literally everything else because you think you know better, like system logging.
Init needs to do system logging when you want to collect it from the daemons stdout, which is the logical place to collect it from. Havin apps handle their own log files is a bad time at best and dangerous at worst.
You are correct ,but again you can just send it to syslog. Just one example of the overwhelming scope creep of systemd.
Recently I’ve been doing scripts on top of systemd to do hacky things with my system and so far I really like it