-
Notifications
You must be signed in to change notification settings - Fork 764
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A cloudy threat looms on the horizon #709
Comments
Isn't there a better idea called "sue the major cloud providers for stealing our patented idea called "FizzBuzz""?
We should sue the major cloud providers instead, but if you want to punish the customers talk to our lawyers to make the most brutal punishment possible while also forcing the customers to keep using our products. |
We need to ask GPT2 to make a decision. The company doesn't have the budget to afford GPT3, let alone GPT4o |
I have access to ChatGPT 4o mini. I asked what should we do. I got this answer: [ChatGPT 4o mini] In this situation, there are several steps you can take:
By taking proactive steps, you can navigate the competitive landscape effectively. Do you think this is a good idea, or should I ask ChatGPT 4o mini again? There's already a PR making our product faster: #694 |
#712 an another cloudy threat loomed on the horizon. |
Yes! I'm particularly interested in option#5. We should send a spy to their headquarters and steal their intellectual property. Nothing can go wrong! |
Two of the major cloud providers are about to release cloud-native FizzBuzz clones that are API-compatible with our stuff. Looks like they're using a lot of our open-core components in their backends.
I suggest we respond by punishing our customers. Shall we switch to the AGPL, SSPL, or Business Source License?
The text was updated successfully, but these errors were encountered: