I understand why this spark conversations about the current Firefox market share situation. But I also believe that Firefox's dominant past plays against when it comes to analyzing the product right now. Firefox is amazing, it works wonderfully, it continues to improve, respects privacy, adopts Mozilla's ethical values. Yes, not many people use it, but criticizing this point so aggressively I think it is also influen…
Thank you, Chris
151–160 of 229 posts
Re: Thank you, Chris
#152just want to give a shoutout to Firefox Focus and whoever is at Mozilla that made it happen. absolutely fantastic no tracking one tab experience that has made a dent in my browser tab management and privacy defaults like nothing else has. thank you!
Re: Thank you, Chris
#153Earlier quoted context omitted.
One area where a company like Firefox could do well is embedded browsers. Some years ago I had a need to embed a browser into a windows app and there were really not many good options available. Mozilla had something (XULRunner) that seemed not maintained anymore. Mozilla could build a better competitor to Electron. That would give them developer mindshare and probably also contributions once companies are building p…
In retrospect, it seems that Mozilla's biggest stumble was their decision to ignore embedding. Around 2009-ish, the decision was made to break any compatibility guarantees for embedding, at first temporarily (which was necessary until new APIs that could support multiprocess in the engine), and then the idea was that you wouldn't embed Gecko at all, and instead use XULRunner. Then XULRunner was killed off for Firefox…
Re: Thank you, Chris
#154Earlier quoted context omitted.
When Firefox decimated Internet Explorer in the 2000s, it was just... better. And I think Chrome had some fairly obvious gains over Firefox and IE which led it to gain market share. I was an early adopter of Chrome, but that was in the days before Google seemed so sinister... I use Firefox now because I care about privacy, and I'd rather use a browser developed by a non-profit that cares about that as well. But I sus…
Firefox was a lot better than IE, but decimated is not the right word. I think it had about 25% market share at its peak? Chrome might be better than Firefox for some use cases, but the difference is definitely not as big as it used to be between Firefox and IE. Yet its market share is way higher. Which leads me to think it's not (just) about being better. I'd guess lock-in/cross-product marketing is another major fa…
I think decimated is the right word, as it seems it took somewhere around 10% of IE's market share.
Re: Thank you, Chris
#155Chris was great from what I have seen, but I think Mozilla needs a CEO that knows how to increase market share.
Mozilla is now openly peeing in Google's punch all the while being dependent on piles of money they take from it. At some point Google will get tired of this and will withdraw from the agreement. They won't be the default search provider, but that will play to their advantage - Firefox out-of-the-box user experience will take a sharp nose dive. Say all you want about DDG and alternatives, but they still can't hold a…
Re: Thank you, Chris
#156just want to give a shoutout to Firefox Focus and whoever is at Mozilla that made it happen. absolutely fantastic no tracking one tab experience that has made a dent in my browser tab management and privacy defaults like nothing else has. thank you!
Re: Thank you, Chris
#157Earlier quoted context omitted.
One area where a company like Firefox could do well is embedded browsers. Some years ago I had a need to embed a browser into a windows app and there were really not many good options available. Mozilla had something (XULRunner) that seemed not maintained anymore. Mozilla could build a better competitor to Electron. That would give them developer mindshare and probably also contributions once companies are building p…
In retrospect, it seems that Mozilla's biggest stumble was their decision to ignore embedding. Around 2009-ish, the decision was made to break any compatibility guarantees for embedding, at first temporarily (which was necessary until new APIs that could support multiprocess in the engine), and then the idea was that you wouldn't embed Gecko at all, and instead use XULRunner. Then XULRunner was killed off for Firefox…
(There’s also not much point to disabling XUL extensions entirely since Firefox now requires extensions to be signed).
Re: Thank you, Chris
#158Earlier quoted context omitted.
Mozilla is now openly peeing in Google's punch all the while being dependent on piles of money they take from it. At some point Google will get tired of this and will withdraw from the agreement. They won't be the default search provider, but that will play to their advantage - Firefox out-of-the-box user experience will take a sharp nose dive. Say all you want about DDG and alternatives, but they still can't hold a…
Say all you want about DDG and alternatives, but they still can't hold a candle to Google's search quality. I'm rather torn on this point. On one hand, yes, DDG for example feels some years behind Google in its relevance ranking. On the other, Google itself has been degrading the quality of its own results with ads, etc. so badly that they've seriously degraded their own "above the fold" relevant results.
The page I was after was not to be found.
Well at least on the first page, I didn't bother checking beyond. Did the !g thing and got the page I wanted straight up first hit.
Here are the searches for reference:
https://duckduckgo.com/?q=maker+pro+install+tensorflow
https://www.google.com/search?q=maker+pro+install+tensorflow
I've tried DDG so many times, but it just doesn't find relevant stuff. Sad, because I don't want to rely on Google.
Re: Thank you, Chris
#159Earlier quoted context omitted.
during Chrome's climb, Firefox was a fairly slow mess and in some ways caused by users having tons of addons enabled at any given time. Firefox was a lot better than IE when Firefox came out (and remained that way even during its slow period), but Chrome was a lot better during its initial rise than both of them too. Firefox is way better from a performance standpoint than it was during Chrome's climb, but Chrome gob…
At this point I honestly wish chrome never happened.
Now at least, users have choice of what they deem the "best browser" to be and I honestly don't think they're inherently wrong for feeling that way. If someone uses Safari, Firefox, Chrome, Edge (though with that last one, I feel for them because it doesn't have the best tab recovery when Edge closes unexpectedly), or some derivative of any of the above, I think they're going to be reasonably okay.
Re: Thank you, Chris
#160Earlier quoted context omitted.
Okay, I'll bite. Having two implementations of a browser engine is a good thing. Without competing implementations, we're writing Chrome apps , not web apps . The important difference there is that monopolies are self-sustaining and that competition prevents Google from exercising complete control over the Web without some other player having a say in it. I think you might realize this, although your GitHub post was…
I answer late because I was blocked for "spamm", anyway here's my long answer. Well, first of all thank you . You actually added intellectual value to the thread and help me better understand others. That said, let's analyse what is right and what might be wrong from your comment. First of all, let's name A the hypothetical scenario where Firefox switch to chromium and maitain a soft fork where disagreement might occ…
But it doesn't. The problem with monoculture is that the bugs in the implementation tend to overrule the standard, and additionally it can make the standard impossible to implement in alternative methodology. The (P)NaCl work was rejected by other browsers because to implement those APIs correctly required you to architect your browser in much the same way as Chrome.
For this reason, the W3C and other standardization forums require at least two independent implementations of a technology to ratify it as a standard: multiple implementations would help clarify where the specification is unclear, but having independent implementations also informs the standardization process on if the architecture is too specific to a particular implementation.