this post was submitted on 21 May 2024
135 points (95.3% liked)
Asklemmy
43992 readers
777 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Microsoft knows that if they start tampering with that they will get into all kind of shit antitrust wise. Proton is a pretty small project from their perspective, so itβs really not worth the risk and/or public backlash.
Sure, but Microsoft has since contributed a lot to Linux and other open source projects. That's not me saying "oh they've changed!", that's me saying they've made it significantly harder on themselves to bring legal action against because they've publicly endorsed and supported the project for so long.
Whatever legal arguments they tried in the past that failed are even weaker now.
Considering that Microsoft has been involved in Linux development for a while now (they added some Linux stuff into Windows via WSL, for example), it would be stupid of them to try and kill it.
Even then you can still have someone read the source and write a spec for a second programmer to write a library. The programmer never saw the source code but it was still useful. Still legal to do this. If someone dumped original source into the projector could be similarly checked for duplication without breaking the law.
Thatβs what LLMs are for
There are techniques to insulate the codebase. For example, you can have one person read the actual leaked code, explain the data structures and algorithms at a high level to a developer, then have the developer implement that logic themselves based only on what they understood from the explanation. I believe this is known as clean-room reverse engineering.