One other factor with Firefox is the use of the platform to push "experiements" and "studies" in their nightly builds, as discussed in these posts:
https://drewdevault.com/2017/12/16/Firefox-is-on-a-slippery-slope.html https://utcc.utoronto.ca/~cks/space/blog/web/FirefoxNoNightly Decisions made by Mozilla on this front indicate an overall willingness to abuse their user base without explicit consent in support of opaque data sharing partnerships and what are essentially affiliate programs to side load code on user computers. -- Darren Spruell [email protected] On Tue, Jun 12, 2018 at 11:25 AM, lampshade <[email protected]> wrote: > Maybe this time mail will be encoded properly. > >>Chrome and Safari both derive from Apple WebKit which itself is a fork >>of the KHTML rendering engine developed by the KDE project, and has >>*always* been, LGPL licensed code since its first release in 1998. >>Yet today, Firefox is held up as the open-source darling and >>Chrome/Safari is seen as the proprietary devil. >>Go figure. :-) > > But still Chrome has a purpose to push away people > from desktop programs to WebApps, because of all the advertisement, > marketing and tracking possibilities WebApps give to the companies, > especially Google. > WebApps also means data is not stored locally, but remotely. > > Not to mention Chrome sends your history to Google > servers when you log in into Google Account(Gmail, Youtube). > > I know some people can write open-source WebApps > and host them on their private servers or at least > paid VPSes, but how many? Not to mention these > WebApps will probably not cover every use-case > and they are going to use some company WebApp > anyway.
