3 ms·
> Now, maybe there's a great reason for this. Maybe they're under NDA and can't reveal part of the schematics. Maybe releasing these schematics would make it su
by autoexec 4y ago
> Now, maybe there's a great reason for this. Maybe they're under NDA and can't reveal part of the schematics. Maybe releasing these schematics would make it super easy for a competitor to completely steal everything. Maybe they are going to release the full schematics and we're waiting on their engineering team and legal team to review them.
I guess I'd question 'fear of competitors' being a "good" reason, but I'd agree with you otherwise. Regardless of what the need for secrecy is, unless it's "we're forbidden by the state" and there's some kind of national security letter involved or "We're doing something illegal and we'd get sued if it were known to the public", why not just tell the public why they can't release the full schematics? What else would prevent someone from talking about why they couldn't talk about something? Refusing to even explain themselves just makes it all seem more suspicious.
- vel0city 4y agoSometimes NDAs prevent even revealing the scope of the NDA, because knowing the scopes of things is then potentially exposing information a party doesn't want known by others. Sure, maybe Framework could just go and state those things, but they're potentially burning their relationships with key partners that might be necessary to make the product at the moment. I'm not arguing this is a good thing, just trying to share some perspective.