With fork I mean, taking the code, forking it, and developing it on your own.
If someone would take the Redis-C lib and the Redis CLI and change it, but keeping Redis unchanged, I would not call that a "Redis fork".
Valkey who is forking Redis and everything, does not depend on Redis (at most cross patching exploits). I would call that a fork.
"Most Firefox code isn't evil."
You are successful, they will change the license, and you're dead - most current fork will not keep up the work because it is too much compared to changing the UI.
"recent web standards" The only reason for these is the cartel of web browser vendors (Google,Apple,Microsoft,Mozilla) to keep out competition. Worked for 10+ years, until Ladybird showed the strategy is flawed.
You are successful, they will change the license, and you're dead
Yeah, but this assumes that Mozilla itself is successful enough to retain the leverage to pull back users towards Firefox.
With the kind of stuff they have been pulling lately it's possible to see a future where one of the above forks (or call-them-what-you-will) gain traction and take users and developers away from Firefox. If this happens, Mozilla deciding to close off the code would just be the last nail in their coffin.
With fork I mean, taking the code, forking it, and developing it on your own.
If someone would take the Redis-C lib and the Redis CLI and change it, but keeping Redis unchanged, I would not call that a "Redis fork".
Valkey who is forking Redis and everything, does not depend on Redis (at most cross patching exploits). I would call that a fork.
"Most Firefox code isn't evil."
You are successful, they will change the license, and you're dead - most current fork will not keep up the work because it is too much compared to changing the UI.
"recent web standards" The only reason for these is the cartel of web browser vendors (Google,Apple,Microsoft,Mozilla) to keep out competition. Worked for 10+ years, until Ladybird showed the strategy is flawed.