<JacobWeisz[m]>
This is a really big one in Microsoft slowly but surely open sourcing their entire legacy Windows platform.
<JacobWeisz[m]>
Legacy comments are one of those concerns Microsoft had about mass open sourcing old code, this seems to be a new approach to solve that issue, they just... deleted them all for now.
<isd>
I vaguely remember hearing about them getting caught with a DEC copyright notice in some of their code once...
<JacobWeisz[m]>
I know I've read about some... unfortunate language and commentary in some of their comments from old leaked source too.
<isd>
can't say I'm surprised they'd be worried about a codebase that old.
<JacobWeisz[m]>
I am very curious about the strategy implications. Does Microsoft believe ESE should be used by some third parties instead of SQL-based databases? Or is this a general push to open source Windows itself, ESE being a significant component in many pieces of that.
Mitar has quit [Ping timeout: 272 seconds]
Mitar has joined #sandstorm
nicoo has quit [Remote host closed the connection]
nicoo has joined #sandstorm
_whitelogger has joined #sandstorm
Mitar has quit [Remote host closed the connection]
Mitar has joined #sandstorm
<xet7>
MS has Open Source .Net Core, VSCode, custom Linux distro for IoT Azure, contributions to Linux kernel, etc etc. It's just more Open Source from MS all the time.
<xet7>
There is also ReactOS already Open Source, and runs some Windows apps. And wine for running Windows apps.
<xet7>
Even if Windows were Open Source, MS would need to support it, release security updates etc
<xet7>
to keep existing apps running
<xet7>
or support compatible Windows container for legacy apps
<xet7>
or just run old Windows software at Azure remotely
<xet7>
MS seems to be hiring Rust devs. Maybe they should switch to Redox OS ;)