cross-posted from: https://yall.theatl.social/post/3229309
From the Atlanta Daily World:
In a surprising yet increasingly common move, Microsoft has quietly dismantled its team dedicated to diversity, equity, and inclusion (DEI). The decision, communicated via email to the affected employees on July 1, cited “changing business needs” as the reason for the layoffs. While the exact number of employees impacted remains unclear, the team’s lead didn’t … Continued
The post Microsoft Says Bye-Bye DEI, Joins Growing List Of Corporations Dismantling Diversity Teams appeared first on Atlanta Daily World.
It makes things worse for projects like emulators, because of any of the leaked code makes its way into their project, they can get sued. Even if it just looks like they used it to develop it, they can get sued. It’s not worth the risk, so projects like emulators will avoid that like the plague.
No, I don’t mean copying code. I mean understanding windows api calls, and how the system works.
Right, but if your code happens to look similar to Windows code (which it will), you’re open to copyright takedowns, even if you didn’t copy a single line. Your best defense is saying you never looked at it.
You’re exhausting.
That’s literally how it works w/ WINE development. Here’s something very related to it on the WINE forums:
It’s a poison pill for WINE to use leaked source code, so the WINE developers have a strict policy against it. I’m guessing most other FOSS projects in the space feel the same way.
I didn’t say use the source. Just see how it works. If you’re trying to emulate the windows api — which is what wine is doing — it helps to have insight.
“Insight” is a liability. The only way this works is if it’s done in a “clean room” setup, which is probably more work than not having any access.
Agree to disagree.