![]() making something that basically amounts to a Chromium skin but with a really good download manager takes a pretty reasonable amount of work.īuilding on top of Firefox is basically a non-starter these days, and forking Firefox just gets you Firefox without even much of a skin. Small rant incoming, but is anyone else tired of every upcoming browser using Chromium? What about forking off Firefox, or creating their own engine?īuilding something on top of Chromium or Blink is relatively easy, and so is building new features that don't require changes in the actual web stack. Nor have I seen any apology after I pointed out in another comment (which you removed btw) how it's patently wrong that PM never published a single CVE.Īnd last question: since you guys are so concerned about security, will you make AutoMod do the same thing when SeaMonkey and Waterfox Classic are mentioned (which are arguably worse security-wise, especially Waterfox Classic which admitted they still have lots of vulnerabilities left unpatched)? Or are you just going to target PM because it's a convenient target? I still don't hear any apology from your mod team for spreading obviously false information about how the browser doesn't support TLS 1.3 and WebP. If it isn't you, then who would it be then? Because hiding behind AutoMod to escape accountability is not cool. There is no future with Mozilla.Īnyway, please answer this question honestly: are you the one who wrote that AutoMod message spreading FUD about *ale *oon? You're my primary suspect because of your dislike of people criticizing Mozilla, and PM is one of the notorious ones calling out their wrong decisions. They can't go back to 52 and use UXP because that would screw over many of their users' profiles, and they can't move forward with Mozilla because it breaks a lot of their things. And look where they are now: perpetually stuck. They should've listened and accepted Moonchild's invitation of collaborating on a XUL-first platform fork, but they didn't. I like SeaMonkey's interface more than *ale *oon, but I'm very pessimistic on whether the former will be able to release a stable 2.57, let alone a version that is on par with mozilla-central. The statement "SeaMonkey 2.53.x uses the same backend as Firefox and contains the relevant Firefox 60.8 security fixes." in their release notes is more of an assurance to those waiting for 2.57 that SeaMonkey is up-to-date with security patches. ![]() If SeaMonkey's stable release right now is truly 60 (which would be 2.57, which is still in perpetual alpha), then we would see e10s, fully functioning WebExtensions, and a fully fleshed Quantum. SeaMonkey's versioning scheme is based on Firefox's.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |