3 ms·
Just to pile it on, I think it's becoming something of a viral force for monoculture, too. 20 years ago, I might occasionally reboot to Windows or fire up a Win
by bunderbunder 7y ago
Just to pile it on, I think it's becoming something of a viral force for monoculture, too. 20 years ago, I might occasionally reboot to Windows or fire up a Windows virtual machine in order to open up the occasional recalcitrant Word document in Word itself. Nowadays, if I'm not running Linux on the metal, then I need to keep some sort of a Linux virtual machine running constantly, because so much software has a hard dependency on either the GNU userland or a Linux kernel feature such as LXC.
This is worrisome to me, because, while GNU/Linux is FOSS, "free and open source" doesn't actually mean "unfettered". A small number of large corporations such as IBM and Google have an outsize amount of influence. Doubly so now that IBM owns Red Hat. And, as the whole GNOME/systemd thing demonstrates, even the non-corporate entities have a lot of opportunity and incentive to engage in rent-seeking behavior now that things have been whittled down to such a tight software monoculture. They'd presumably not have even attempted such a thing as taking a hard dependency on systemd if maintaining decent compatibility with FreeBSD (or any other OS) were still a relevant priority.
- aerique 7y agoYes, this. And SystemD adds to this monoculture (as does Docker).
- bunderbunder 7y agoI realize I'm picking a nit, but I think that, in this situation, it reflects a distinction that's worth making: Systemd and Docker do entrench the monoculture, but they can only have that effect because the monoculture is already so well-established. If this were EEE, they'd be part of the transition to the third E.