2 ms·
The current title doesn't seem to match the post that much better either. Clicked to see what awesome new idea about a next generation browser I will encounter.
by galistoca 11y ago
The current title doesn't seem to match the post that much better either. Clicked to see what awesome new idea about a next generation browser I will encounter. Was not quite what they were talking about.
- ygjb 11y agoSee my other comment in the thread. Palemoon lacks the resources to drive a modern browser fork. Rather than trying to maintain the current fork they have, the proposal is to either rebase, or create a new fork (or some other definition of "re-fork" that I am not able to parse). The irony in this is that the reason they need to do this is because they were deeply unhappy with the changes Mozilla was making to correct technical debt due to the age of the codebase. Those changes allowed the features to be implemented that the Palemoon devs are lamenting in the post. I would also like to take this moment to bang the security drum and remind everyone that Palemoon has been developing new browser features for 6 years, while taking up some, but not all, Mozilla security fixes, without a security team of their own. Read into that as you will, but also consider how successful people have been in forking Chromium (or just grab a bowl of popcorn and read through https://twitter.com/taviso https://twitter.com/taviso if you don't know the history).