- Some kind of MS branded Linux, that offers improved security/performance/usability etc. it’ll offer full compatibility with existing distros like Debian that devs are already familiar with, but it’ll come pre-setup on windows and it’ll have an amazing integration with GitHub, VSCode and azure, and probably their K8s product too. Much like VSCode they’ll use their influence to get devs used to using it. They’ll probably sponsor a bunch of major OSS projects to use it and start offering features specific to it, bits of it will be “open sourced soon” or similar. The position of power and control will be exerted over it-much the same way Google does with chrome and how that is “open source”.
- a linux compatible api layer over windows, with the angle of “no reason to need Linux anymore”, they’ll angle for large enterprise customers first, offering a Linux-compatible experience, to convert them. Similar experience with above, where the end to end (local to cloud) experience will be the focus. Once again they’ll integrate with existing tooling and major OSS players with the same goal-be so seamless and tightly integrated, and “works with existing tools” that devs will flock to it the way they do with chrome. Orgs and projects will switch to supporting it, probably because the overall experience is superior.
That’s a couple of ideas off the top of my head, we could probably all come with some more scenarios.
- Some kind of MS branded Linux, that offers improved security/performance/usability etc. it’ll offer full compatibility with existing distros like Debian that devs are already familiar with, but it’ll come pre-setup on windows and it’ll have an amazing integration with GitHub, VSCode and azure, and probably their K8s product too. Much like VSCode they’ll use their influence to get devs used to using it. They’ll probably sponsor a bunch of major OSS projects to use it and start offering features specific to it, bits of it will be “open sourced soon” or similar. The position of power and control will be exerted over it-much the same way Google does with chrome and how that is “open source”.
- a linux compatible api layer over windows, with the angle of “no reason to need Linux anymore”, they’ll angle for large enterprise customers first, offering a Linux-compatible experience, to convert them. Similar experience with above, where the end to end (local to cloud) experience will be the focus. Once again they’ll integrate with existing tooling and major OSS players with the same goal-be so seamless and tightly integrated, and “works with existing tools” that devs will flock to it the way they do with chrome. Orgs and projects will switch to supporting it, probably because the overall experience is superior.
That’s a couple of ideas off the top of my head, we could probably all come with some more scenarios.