All it takes is to look around at what Microsoft is doing to gestures vaguely to see the writing on the wall for how Microsoft sees Linux.
Advertisements on the home screen? Advertisements on the every screen? Login darkpatterns? Configuration resets on updates? Forceful browser choices? Forced updates? UEFI shenanigans? Boot manager shenanigans?
As proven by OEM distributions on by gone netbooks, and Android flavours, OEMs will always do what they do best.
In what concerns Windows, unfortunately it appears only Azure, Office and XBox matter now.
LOL
Its amazing how easy it is. I guess if you spend your entire history being a shitty company and then spend a couple of years pretending to be marginally less shitty then you can dupe a bunch of people.
I do think they had commercial aspirations work systemd, but more about "being the company that invented..." Than a direct cash cow.
This is in contrast to the play canonical makes with snaps that has 30% app store tax written all over it.
Do you have some links to share?
Now working on a replacement to systemd-tmpfiled for OpenRC.
Run these sysvinit, OpenRC and maintain systemd as well at this shop.
Also who are these people who have complicated sysv scripts? I've heard this for years and never really understood it. One script per service with a stop and start command (and maybe a status if you want to get fancy) and runlevel definitions that start and stop them. It's not rocket surgery, and it's a hell or a lot easier to debug than a declarative system definition.
Into correct imperative sequence. That’s the whole point of declarative things.
You can’t feasibly write it correctly otherwise. You are writing programming languages over assembly for largely this same reason.
FreeBSD has Mewburn rc not van Smoorenberg rc and was thus inherently better in this regard until the middle of 2014 (https://unix.stackexchange.com/a/480897/5132). But even FreeBSD has some large rc scripts, particularly in the networking and the HID parts such as Bluetooth and configuring all attached keyboards; albeit that the FreeBSD style guidelines mean that they are more legible than the nightmare Debian (et al.) ones.
Startup is ultimately a complex problem. There is no magic, just race conditions which maybe became more apparent. LVM may or may not be used, and takes time to start up. Do you wait for it? Ditto wireless networks. And how do you handle devices being hotplugged? Setups vary widely, and can be dynamic.
??
Mount filesystem, start networking, start networking daemons, update crappy gtk stuff, run rc.local.
What is so complex ?
then i start to find out it is full of rando backdoors intended for VMs, which will run just the same on your bare metal. For example, just to list the very last one, you can inject smbios data that will be parsed to create files in your system. very convenient to drop passwords and keyfiles around a vm... unless it is the firmware on your actual bios doing the same. And we know how common persistence via bios is. sigh.
but as you mention correctly, it have crushed and dominated linux. so i guess i just waste a week or some working around those things later, as usual.