β² 1447 βΌ Linux source code leaked (media.piefed.zip) submitted 1 day ago by linsenchip@piefed.zip to c/linuxmemes@lemmy.world 138 comments fedilink hide all child comments
[β] spicehoarder@lemmy.zip 16 points 1 day ago (3 children) I think it was that the XP source was leaked. There was a huge deal because those who saw it were highly discouraged from contributing to wine. permalink fedilink source parent hideshow 6 child comments replies: [β] aim_at_me@lemmy.nz 2 points 15 hours ago ReactOS also. permalink fedilink source parent [β] TrickDacy@lemmy.world 6 points 1 day ago (2 children) those who saw it were highly discouraged from contributing to wine. Can you expand on that a little? permalink fedilink source parent hideshow 4 child comments replies: [β] brandon@piefed.social 21 points 1 day ago (1 child) The potential for copyright infringement (or at least the appearance of copyright infringement) would be too high. Better to keep a "clean room" approach in the wine project to avoid attracting Microsoft's ire. permalink fedilink source parent hideshow 2 child comments replies: [β] TrickDacy@lemmy.world 3 points 1 day ago Ah, that definitely makes sense. Thanks! permalink fedilink source parent [β] 4am@lemmy.zip 13 points 1 day ago (1 child) WINE is a compatibility layer (famously, WINE Is Not an Emulator) for Windows APIs on posix OSes; most notably this allows you to run Windows applications on Linux. Microsoft would truly love to beat WINE to death with a legal sledgehammer but so far they do not have the legal ground, as WINE is developed based on public knowledge and Microsoft famously keeps their source code closed. If you saw the Windows source code, and then you contributed to WINE, it is possible Microsoft could make the legal argument that WINE was using stolen trade secrets, even if the verbatim source code was added to the WINE codebase. Whether or not that would have worked for Microsoft is up in the air; but the WINE project didnβt want to find out the hard way. permalink fedilink source parent hideshow 2 child comments replies: [β] TrickDacy@lemmy.world 4 points 1 day ago Gotcha. Thank you. permalink fedilink source parent [β] AnUnusualRelic@lemmy.world 1 point 1 day ago The source code for windows has always been fairly widely available among industrial actors (provided suitable NDAs were signed). So, nothing exceptional there. permalink fedilink source parent
[β] TrickDacy@lemmy.world 6 points 1 day ago (2 children) those who saw it were highly discouraged from contributing to wine. Can you expand on that a little? permalink fedilink source parent hideshow 4 child comments replies: [β] brandon@piefed.social 21 points 1 day ago (1 child) The potential for copyright infringement (or at least the appearance of copyright infringement) would be too high. Better to keep a "clean room" approach in the wine project to avoid attracting Microsoft's ire. permalink fedilink source parent hideshow 2 child comments replies: [β] TrickDacy@lemmy.world 3 points 1 day ago Ah, that definitely makes sense. Thanks! permalink fedilink source parent [β] 4am@lemmy.zip 13 points 1 day ago (1 child) WINE is a compatibility layer (famously, WINE Is Not an Emulator) for Windows APIs on posix OSes; most notably this allows you to run Windows applications on Linux. Microsoft would truly love to beat WINE to death with a legal sledgehammer but so far they do not have the legal ground, as WINE is developed based on public knowledge and Microsoft famously keeps their source code closed. If you saw the Windows source code, and then you contributed to WINE, it is possible Microsoft could make the legal argument that WINE was using stolen trade secrets, even if the verbatim source code was added to the WINE codebase. Whether or not that would have worked for Microsoft is up in the air; but the WINE project didnβt want to find out the hard way. permalink fedilink source parent hideshow 2 child comments replies: [β] TrickDacy@lemmy.world 4 points 1 day ago Gotcha. Thank you. permalink fedilink source parent
[β] brandon@piefed.social 21 points 1 day ago (1 child) The potential for copyright infringement (or at least the appearance of copyright infringement) would be too high. Better to keep a "clean room" approach in the wine project to avoid attracting Microsoft's ire. permalink fedilink source parent hideshow 2 child comments replies: [β] TrickDacy@lemmy.world 3 points 1 day ago Ah, that definitely makes sense. Thanks! permalink fedilink source parent
[β] TrickDacy@lemmy.world 3 points 1 day ago Ah, that definitely makes sense. Thanks! permalink fedilink source parent
[β] 4am@lemmy.zip 13 points 1 day ago (1 child) WINE is a compatibility layer (famously, WINE Is Not an Emulator) for Windows APIs on posix OSes; most notably this allows you to run Windows applications on Linux. Microsoft would truly love to beat WINE to death with a legal sledgehammer but so far they do not have the legal ground, as WINE is developed based on public knowledge and Microsoft famously keeps their source code closed. If you saw the Windows source code, and then you contributed to WINE, it is possible Microsoft could make the legal argument that WINE was using stolen trade secrets, even if the verbatim source code was added to the WINE codebase. Whether or not that would have worked for Microsoft is up in the air; but the WINE project didnβt want to find out the hard way. permalink fedilink source parent hideshow 2 child comments replies: [β] TrickDacy@lemmy.world 4 points 1 day ago Gotcha. Thank you. permalink fedilink source parent
[β] AnUnusualRelic@lemmy.world 1 point 1 day ago The source code for windows has always been fairly widely available among industrial actors (provided suitable NDAs were signed). So, nothing exceptional there. permalink fedilink source parent
