Great talk imo, my TLDR would be :
> systemd is not the best it could be, but it's there.
> distros patting themselves on the back because they don't use it means they haven't listened to actual needs and stayed behind.
> death threats over software that nobody else tried doing are ridiculous
Don't forget the gaslighting with "software has bugs" and "you just dont like change", while glossing over legit complaints about the outright narrow minded design of the system that is actively harmful in some cases (systemd-timesyncd, I'm looking at you).
Personally, the video made me rather angry because all he does is set up straw men and knock them down using the same terrible pro-systemd arguments that get trotted out every time someone has a legit problem with its design.Some of the distros that use systems like runit and openrc are using those sustems because systemd doesn't fit their technicals needs, and likely won't ever because of designs that are made without community input.
Oh, sure, he mentioned the Debian developer resignations, but outright failed to point out the reason why they resigned: systemd was being railroaded into the system as a political move rather than being judged on its technical merits.
> Oh, sure, he mentioned the Debian developer resignations, but outright failed to point out the reason why they resigned: systemd was being railroaded into the system as a political move rather than being judged on its technical merits.
No. Ian resigned because he tried to ignore systemd's technical merits and tried to used political moves (GR process) to to kill it. As a result, most of Debian's community told him to top messing around with politics. Ian's resignation letter [1] explicitly says that:
> I should step aside to try to reduce the extent to which conversations about the project's governance are personalised.
[...]
> The majority of the project have voted to say that it was wrong of me to bring this GR at this time.
Please stop saying systemd was being railroaded. I have no idea what was going on in Redhat (I do not follow their mailing lists), but at least in Debian, it got on its own technical merits, and Poettering had no special influence there.
(That is not to say it is without problems; there are plenty of them. Still, the lesser of evils...)
> Please stop saying systemd was being railroaded. I have no idea what was going on in Redhat (I do not follow their mailing lists), but at least in Debian, it got on its own technical merits, and Poettering had no special influence there.
Systemd got in on its merits in Fedora as well. (It had to — no amount of railroading is going to overcome something totally dysfunctional, and Fedora was the first adopter.) As I recall, the transition was fairly smooth.
I've been using it for personal projects and it's been quite fun !
The comments about Postgres and database XX vs ArangoDB are always the same, this is a choice depending on the use-case, if you have a vague scenario, ArangoDB has good performance on a wide array of use cases.
On a personal note, the main downside is not having any ORM for Golang for example, Node.js doesn't have any worth considering too.
Python seems to have arango-orm, which makes it simpler for small projects to integrate it.
Another improvement could be the graph visualization, simplifying the setup to use another solution would be nice.
https://soundcloud.com/gby/kernel
https://soundcloud.com/gby/airglow-fire-gby-remix
https://soundcloud.com/gby/euv
https://soundcloud.com/gby/mullet-discotheque
https://soundcloud.com/gby/2jz-1
https://soundcloud.com/gby/childhood-startup