3 ms·
I’m not sure why are you downvoted — yeah the “rewrite everything in rust” hype is bad/annoying (and no, I don’t have any problem with rust), but systemd simply
by kaba0 6y ago
I’m not sure why are you downvoted — yeah the “rewrite everything in rust” hype is bad/annoying (and no, I don’t have any problem with rust), but systemd simply should not have been started in C. It replaced goddamn shell scripts so performance can’t really be a good argument pro, but a not too scripty managed language would have more than enough performance.
- nn3 6y agoIf it had been written in rust or go, we already would have hundreds of MB worth of systemd binaries on our disks, like some other popular packages. People all the time complain about systemd bloat, but it's very likely that in those languages it would be far worse.
- kaba0 6y agoI don’t believe people complain about systemd binaries’ sizes at all. They complain about bloat (in my opinion wrongly) in terms of systemd incorporating more and more features that often seems orthogonal to an init system. But often these are not part of systemd itself, but created only under the same project.
- CameronNemo 6y agoWhat language would have been appropriate in 2013?
- kaba0 6y agoWell, C++ had been around, but there were plenty of managed languages also. I will be hated for this, but perhaps even Java would have been appropriate if one sets the heap size appropriately, I believe the GCs were already quite good then; and it wouldn’t have to create too much garbage so I think it could get away with only a bit of memory. The only problem is the not too comfortable way to do C calls.
- fl0wenol 6y agoUnix sockets aren't in the standard java libraries either, which probably meant it was a non-starter.
- themadsens 6y agoGolang comes to mind. Gobs of C boilerplate could have been avoided. Docker is written in Go after all and was first released in 2013
- CameronNemo 6y agoGo was very immature at the time. Literally a brand new language.