For me, it's a privacy concern. Closed source means only one company is fixing vulnerabilities, whereas open source invites security researchers to find and fix issues quicker. Fewer security gaps == less privacy risk.
I've heard that argument before, but has that actually been demonstrated? Ability to look at the code (especially in the age of AI) means that security researchers aren't the only ones who can look for bugs. For example, look at the bugs like copyfail that AI has recently uncovered in the Linux kernel.
> A new project based on our code might implement features that are fundamentally in opposition to our ethics (e.g., damaging to privacy, human rights or to the environment). Even though we would not be associated with the project in any way, it can deeply affect how people see Vivaldi (and how we see ourselves), damaging a reputation we have taken pains to earn.
> You can’t test drive open-source and then close everything back off if it turns out that open-source isn’t working out.
At the same time they express regret that the Presto engine from their Opera roots didn't get open-sourced. Which was much more novel than just a Chromium re-skin.
The entire article can be summarized as "we worry that others might make a better product off our code" and "can't be arsed to meet the quality standards of the free software community".
> "can't be arsed to meet the quality standards of the free software community".
Lol literally all the code is visible. Also all the Firefox forks I've seen are low-effort forks that even piggyback off Mozilla's servers for stuff like user authentication.
Furthermore I don't see a clear business model there that isn't about injecting ads.
Vivaldi has been doing exactly this for years now
Can I ask why?
For me, it's a privacy concern. Closed source means only one company is fixing vulnerabilities, whereas open source invites security researchers to find and fix issues quicker. Fewer security gaps == less privacy risk.
I've heard that argument before, but has that actually been demonstrated? Ability to look at the code (especially in the age of AI) means that security researchers aren't the only ones who can look for bugs. For example, look at the bugs like copyfail that AI has recently uncovered in the Linux kernel.
2 replies →
like dude. do u have to?
Great answer ..
https://vivaldi.com/blog/technology/why-isnt-vivaldi-browser...
It's open in all of the ways that matter, basically they just want to protect their look and feel.
Some of their arguments are ridiculous.
> A new project based on our code might implement features that are fundamentally in opposition to our ethics (e.g., damaging to privacy, human rights or to the environment). Even though we would not be associated with the project in any way, it can deeply affect how people see Vivaldi (and how we see ourselves), damaging a reputation we have taken pains to earn.
> You can’t test drive open-source and then close everything back off if it turns out that open-source isn’t working out.
At the same time they express regret that the Presto engine from their Opera roots didn't get open-sourced. Which was much more novel than just a Chromium re-skin.
The entire article can be summarized as "we worry that others might make a better product off our code" and "can't be arsed to meet the quality standards of the free software community".
No thank you.
Are you reading the same article?
> "can't be arsed to meet the quality standards of the free software community".
Lol literally all the code is visible. Also all the Firefox forks I've seen are low-effort forks that even piggyback off Mozilla's servers for stuff like user authentication.