![]() It's hard to think how far we came since the 1990's - and how wonderful the emergence of Opera and Firefox were before Opera fell off the bandwagon.įor example, many of my cousins are in IT jobs, and most if not all don't give a shit about what browser they use or what they recommend because they don't specialise in web development. then we have the Wonderful Widevine which screws small browsers for no other reason than Google wanting to rule the world. This happened with Android - Google Play Services came along. People worship Chrome, and Google (who obviously support Open Source) - but fail to realise that Google ONLY supports Open Source at the time that it benefits them in gaining Market share, then when they have market share, they scupper the project and laugh their heads off. I also get angry that my son's Thai school teaches them about Email (Email means Gmail) and maps (Maps means Google) and search (search means Google) and operating systems (operating systems = Windows) and text editors (Text Editors = Microsoft Office). Mostly I get sick of everyone who says they don't care - who encourage Google to dominate, and then scream blue murder when they realise how bad it is to use something like Youtube on a device where they have no control and get forced to watch 5 minutes of ads before they can watch a 3 minute video. I LFMAO for people who use Ubuntu and get forced to install Chromium as a SNAP. I LFMAO when Google started screwing Chromium out of the Google API loop. Mozilla can barely keep up with Chrome despite having hundreds of engineers to work on Firefox. Since you're not simply building on top of it, but rather making actual changes to Firefox, you have way more work to keep your changes ported to newer Firefox versions than someone who builds something on top of Chromium or Blink.Ĭreating your own engine would take a bazillion person-hours of work, at least if you want it to be competitive. 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 |