3 ms·

I fully agree with this article. I respect people choosing products based on ideality, but I personally will just use what suits my demand/preference best. Wh

I fully agree with this article. I respect people choosing products based on ideality, but I personally will just use what suits my demand/preference best. When I first switched from IE to Firefox 1.5, it's because it has tabs. And I loved it more and more once I figured out how well-built it is and how powerful addons can be. When Chrome firstly came, it was pretty bad in term of functionality. The extension system is weak (compared to what Firefox can offer at the time), it lack TONS of what I personally consider as "essential features" (font settings for different languages is a big one for me as a non-Latin character user, for example), so I continued to use Firefox. But Chrome catched up very quickly. Today, the features of two browsers are basically on par in my user case, especially after Firefox switched to WebExt (which I think is the right direction, by the way). I started to use Chrome more and more due to some small details, like better sync experience etc. Again, purely personal choice based on my heavy use of both. Another thing that pushed me away from Firefox is my personal experience in bug reporting. I'm not a software developer, but I do report bugs semi-frequently. I feel like I was treated better in Chromium project than Firefox's one. I have lots of unhappy experiences there (the one that I still can't get over is that they won't fix a video playback bug that affects all Win7 + nVidia GPU users [1]). I think in Chromium everytime you report a bug with clear repro steps, there will at least an employee (or volunteer? Not sure) that will attempt to repeat your steps and attach a screencat of that in 1-2 days. It feels good. [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1410693 https://bugzilla.mozilla.org/show_bug.cgi?id=1410693

sametmax 8y ago
People always say "we can't do anything about it" when some bad situation happen. Except it happens because it emerges from the collective behavior. Now, one can't fight a all the fights, and I don't think somebody that decides to avoid this one is a bad person. But one should definitly pick up some fights. Choose some things to pay for, decide some things to consume or be part of, not just by the nature of it, but by the consequences of doing so. Although I do think like in the article that it's better to fight _for_ something than _against_ something. Anyway, if one doesn't makes, on daily basis, regular, endless, conscious choices, one is not taking part of the world but is just passively living in it. And that's how we fail to build a society.
- fireattack 8y ago
  We don't necessarily agree on "what is bad" in this case, so I will leave that alone.
  - sametmax 8y ago
    Nobody agree on that. Bad and good doesn't really exist, it's just a line we draw so it's ok. That kinda of my first point really.
ginko 8y ago
Looking at your Win7+nVidia bug, I'm kind of confused why you would expect Firefox to fix this when this seems to be a bug in the nVidia graphics driver.
- fireattack 8y ago
  It's hard to define it as an nVidia bug or a browser bug. You may say it's an nVidia bug because it only happens on nVidia; but then you can also say it's a "Win 7 bug" because it only happens on Win7. Anyway, as a fact: it works fine in IE and Chrome (after they fixed it). So at very least, it is fixable on browser's end. It also works fine in any video player you can think of. Also, from what I can see, neither Chromium dev nor Firefox dev claim it's an "nVidia bug". Chromium dev just went ahead and fixed it. Firefox dev said they're not going to fix it because (from previous ticket [1]) "We don't intend to add new features such as this code is only used on Windows 7." Which IMHO makes no sense because when this bug firstly appeared, it was 3-4 years ago; and Win 7 is still one of the most used OS and is in the supported OS list of Firefox. [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1161349#c46 https://bugzilla.mozilla.org/show_bug.cgi?id=1161349#c46
  - Yoric 8y ago
    It's a problem of resources. There are simply not enough devs to do everything. So Mozilla needs to prioritize bugs and features aggressively.

sametmax 8y ago

People always say "we can't do anything about it" when some bad situation happen. Except it happens because it emerges from the collective behavior. Now, one can't fight a all the fights, and I don't think somebody that decides to avoid this one is a bad person. But one should definitly pick up some fights. Choose some things to pay for, decide some things to consume or be part of, not just by the nature of it, but by the consequences of doing so. Although I do think like in the article that it's better to fight _for_ something than _against_ something. Anyway, if one doesn't makes, on daily basis, regular, endless, conscious choices, one is not taking part of the world but is just passively living in it. And that's how we fail to build a society.

fireattack 8y ago
We don't necessarily agree on "what is bad" in this case, so I will leave that alone.
- sametmax 8y ago
  Nobody agree on that. Bad and good doesn't really exist, it's just a line we draw so it's ok. That kinda of my first point really.

ginko 8y ago

Looking at your Win7+nVidia bug, I'm kind of confused why you would expect Firefox to fix this when this seems to be a bug in the nVidia graphics driver.

fireattack 8y ago
It's hard to define it as an nVidia bug or a browser bug. You may say it's an nVidia bug because it only happens on nVidia; but then you can also say it's a "Win 7 bug" because it only happens on Win7. Anyway, as a fact: it works fine in IE and Chrome (after they fixed it). So at very least, it is fixable on browser's end. It also works fine in any video player you can think of. Also, from what I can see, neither Chromium dev nor Firefox dev claim it's an "nVidia bug". Chromium dev just went ahead and fixed it. Firefox dev said they're not going to fix it because (from previous ticket [1]) "We don't intend to add new features such as this code is only used on Windows 7." Which IMHO makes no sense because when this bug firstly appeared, it was 3-4 years ago; and Win 7 is still one of the most used OS and is in the supported OS list of Firefox. [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1161349#c46 https://bugzilla.mozilla.org/show_bug.cgi?id=1161349#c46
- Yoric 8y ago
  It's a problem of resources. There are simply not enough devs to do everything. So Mozilla needs to prioritize bugs and features aggressively.