Re:Replit used legal threats to kill my open-source project
by truncate on Tuesday June 08, 2021 @01:30AM
(#27430944)
I'd add that its not uncommon to see same flaws that you'd naturally add when working on similar kind of product
So just saying it has the same flaws as my product by no means implies anything. Very well may mean that the other person didn't notice it or de-prioritized it, just like you when you started the project (which is why the flaw exists in my product at first place).
I understand that you may not be able to describe the invisible long-term proprietary flaws for a number of possible reasons, but can you ballpark the number of these critical flaws that are the unique IP of replit? Or at least the relevant number of times when the code in this recent open source software overlapped with years-old mistakes in the Replit code base that are so crucial that they must be protected?