[deleted]
Chrome is Not the Standard
71–80 of 465 posts
Re: Chrome is Not the Standard
#72I know they screwed up recently with the Mr. Robot malware, but I think it's really important for developers to get behind Firefox again. As the American government fails to provide any sort of check on its behemoth corporations (Apple, Google, and Microsoft) and to protect consumer privacy, Firefox is basically the last contender for real consumer protection standing.
I’ve found a lot of people are quite naively idealistic around browser development. The rendering, JS engines in Firefox and Chrome are state-of-the-art and take small armies to build and maintain. Mozilla has to strike a balance between revenue seeking and consumer protection seeking behavior that I would imagine is quite difficult to maintain. Lots of people here additionally are up in arms their incredibly specifi…
>>I’ve found a lot of people are quite naively idealistic around browser development.
So it is naive to hold a Non-Profit to their foundational mission statement and goal? Their Manfeisto?
Mozilla is not, or rather used to not be, just a For-Profit Software firm making a browser. They were a Non-Profit Foundation started to advance ideological and philosophical ideas, namely Open Web Standards and Access for all.
It seems like you are perfectly find with Losing the Mozilla Foundation, and replacing it with Mozilla Corporation the software developers that make a commercial browser.
Maybe FireFox 60 should just go closed source and charge $40 a download
Re: Chrome is Not the Standard
#73Earlier quoted context omitted.
> The only way to disable Pocket was to go into "about:config", as the option was not available in the "Extensions" toolbar. This isn't exactly correct. The Pocket integration did absolutely nothing at all until and unless you tried to use it. So by "disabling" it from about:config all you did was to remove the icon.
That isn't correct. Try the new mobile Firefox. Buying Pocket signalled that if you can take the right Mozillan to lunch, you can get an early exit. That did not solve the problem. It's still impossible to remove Pocket.
I think you misunderstood me. The Pocket integration in Firefox does literally nothing (not even a single network request) if you don't actively try to use it. So by "remove Pocket" or "disable Pocket" all you really mean is "hide the icon" because there really is no difference.
Re: Chrome is Not the Standard
#74Earlier quoted context omitted.
> The only way to disable Pocket was to go into "about:config", as the option was not available in the "Extensions" toolbar. This isn't exactly correct. The Pocket integration did absolutely nothing at all until and unless you tried to use it. So by "disabling" it from about:config all you did was to remove the icon.
That isn't correct. Try the new mobile Firefox. Buying Pocket signalled that if you can take the right Mozillan to lunch, you can get an early exit. That did not solve the problem. It's still impossible to remove Pocket.
yes, this is the part that bugs me.
they solved the privacy concern in a very awkward manner (via acquisition) but not the user choice concern. it is impossible to believe that pocket is so integrated into the codebase that it cannot live as a removable addon. it was an addonafter all. fwiw, firefox sync should also be a removable addon.
i am fine with mozilla installing these as removable addons at major version upgrades. i am not fine with silently side-loading and permanent non-removable integration. i need my tools to be secure, reliable and predictable.
Re: Chrome is Not the Standard
#75Standards don't matter, interoperability and openness are what matter. Standards are a means to that, but it's perfectly ok for one vendor to add features and do experiments, that is how progress is made, deviation/extension, adoption, analysis, and finally after all of that standardization. A standard without vendors pushing the limits is the hallmark of a dead technology.
Re: Chrome is Not the Standard
#76Earlier quoted context omitted.
Lest we forget: A third party company (funded by venture capital) created something called "Pocket", which allowed you to save any article you were reading to their service. Pocket had an extension that you could choose to download & enable on your Firefox browser. For apparently no reason at all, in June 2015, Mozilla integrated the proprietary Pocket into their open source browser, not just as an optional extension…
> The only way to disable Pocket was to go into "about:config", as the option was not available in the "Extensions" toolbar. This isn't exactly correct. The Pocket integration did absolutely nothing at all until and unless you tried to use it. So by "disabling" it from about:config all you did was to remove the icon.
Sure, but until you do Firefox comes bundled with an ad for Pocket in the toolbar at all times.
Re: Chrome is Not the Standard
#77Chrome is the de facto standard at this time and all of the irrelevant, hyperbolic nitpicking and dubious conjecture isn't going to change that. But here's a thought: WebKit and Chromium (and Blink) are open source, so maybe don't worry about it? Furthermore, if all browsers don't work the same then that's a problem for developers. If we can't have that - I'd rather see just one browser engine in use by the majority…
That would be great if Chromium/Chrome used WebKit, they dont. They stopped using Webkit years ago
Re: Chrome is Not the Standard
#78Earlier quoted context omitted.
No and I think your opinion is harmful. IE literally refused to implement standards, rendered broken dom elements, allowed for proprietary native extensions and had many different apis for them. They had 90% of the market share and no other viable platforms. This meant developers built things which exploited these broken features causing huge compatibility issues when they aren’t (every other browser). A simple lack…
Apple is doing similar stuff by refusing to implement the payment request API and instead implementing their proprietary Apple Pay API. So you can use one API to target Chrome and Firefox and another for Safari. This is starting to sound a bit like IE. They were invited to join the working group for Payment Request and decided not to take part.
You can argue that they're not implementing $thing-you-like but lets be real; you can't compare IE to anything if you don't include the market share.
IE was harmful because it had such incredible market share and could do what it wanted with that.
Re: Chrome is Not the Standard
#79Earlier quoted context omitted.
No and I think your opinion is harmful. IE literally refused to implement standards, rendered broken dom elements, allowed for proprietary native extensions and had many different apis for them. They had 90% of the market share and no other viable platforms. This meant developers built things which exploited these broken features causing huge compatibility issues when they aren’t (every other browser). A simple lack…
Apple is doing similar stuff by refusing to implement the payment request API and instead implementing their proprietary Apple Pay API. So you can use one API to target Chrome and Firefox and another for Safari. This is starting to sound a bit like IE. They were invited to join the working group for Payment Request and decided not to take part.
The Payment Request API is supported in the Safari Technical Preview and enabled by default since Release 44.
https://webkit.org/status/#feature-payment-request https://developer.apple.com/safari/technology-preview/releas...
Re: Chrome is Not the Standard
#80Earlier quoted context omitted.
> The only way to disable Pocket was to go into "about:config", as the option was not available in the "Extensions" toolbar. This isn't exactly correct. The Pocket integration did absolutely nothing at all until and unless you tried to use it. So by "disabling" it from about:config all you did was to remove the icon.
That isn't correct. Try the new mobile Firefox. Buying Pocket signalled that if you can take the right Mozillan to lunch, you can get an early exit. That did not solve the problem. It's still impossible to remove Pocket.
Yes, the latest mobile Firefox does make network requests. When Firefox updated, I got a "recommended by Pocket" section full of ads and click bait. I do not want that.
And it's on about:blank just like when Chrome started capping up the blank page. I had to install a script to load an actual blank HTML page because about:blank isn't blank.