Hacker News new | ask | show | jobs
by kibwen 3694 days ago
Having a ten year-old bug isn't a mark of shame, if anything it's laudable when a project doesn't take the easy way out by silently closing ancient bugs like most projects do. Bugs should be fixed according to importance and priority, not simply according to age.
1 comments

The problem is that "importance and priority" are pretty much subjective terms, for example, for many people Hello or Pocket were everything but a priority.
The solution is that it's an open source project. If you disagree with the priorities of the other developers, then you are empowered to take the initiative.
Okay, I would like to remove Hello and Pocket from Firefox. Do you think Mozilla will merge my pull request that I am empowered to initiate?
As though I said anything about merging into upstream, or about Hello/Pocket, or about "open source" meaning "dictating development with random patches". :P But sure, if there were a ten year-old bug about removing them, then I would certainly expect them to welcome such a patch.
I guess we're not understanding each other. My point is that Mozilla's development of Firefox is no longer user-driven. Instead it's about what Mozilla thinks users should want, and they can take it or leave it, and if it helps Mozilla make money, users should want it.

Despite vocal and repeated requests and complaints, Mozilla refuses to back down and remove things that users did not ask for and do not want; instead Mozilla does things like sneak Pocket support in in a point-release without any advance warning or any chance for the community to give feedback. And note that Pocket has had a fully functional Firefox extension ever since it was Read-It-Later--there was absolutely no technical reason to build in support for Pocket and deprecate the extension.

Mozilla has never been forthcoming about the real reason for doing this. In fact, the few Mozillians who have spoken about it seem to have had no idea why it happened, either.

Instead all we get is vague "people want to save things, this makes it easier for people to save things" statements. Well, people want to use Facebook, too: where is the built-in Facebook plugin? Where's the built-in Netflix extension? Amazon shopping support? etc. Clearly the decision to build in new Pocket code had nothing to do with a principled policy of making things easier for users.

The only reasonable conclusion is that Mozilla cut a deal and is getting money for it. And if that is the case, what is to stop them from doing the same for anything else? What if Microsoft cuts a deal to build in Bing support? etc.

  > where is the built-in Facebook plugin?
Years ago Facebook Messenger was actually built into Firefox. I remember using it myself, but have no idea what's become of that effort since then. See https://www.facebook.com/notes/facebook-engineering/under-th...

  > Where's the built-in Netflix extension?
Users demanding Netflix support is literally the reason why Mozilla was strongarmed into adding support for EME, despite trying to hold out against it for so long.

  > Amazon shopping support?
Click in the search box, type a query, and at the bottom of the suggestions dropdown you'll see that Amazon is one of the search engines supported out-of-the-box. I actually use this fairly regularly.

  > What if Microsoft cuts a deal to build in Bing support?
Just like Amazon, Bing is already supported out-of-the-box, as is Google, Yahoo, DuckDuckGo, eBay, Twitter, and Wikipedia. Mozilla has regional partnerships where they get paid to install such search engines, so you'll get Baidu as your default in China and Yandex as your default in Russia. These even vary per platform: in the US, Google is the default on Ubuntu, and Yahoo is the default on Windows. If Yahoo collapses within the next few years, I fully expect Microsoft to begin paying Mozilla to make Bing the default on Windows.

These default search engines are how Mozilla makes 95% of its income (donations are basically a drop in the bucket, and because of tax laws they aren't allowed to use donation funds to finance Firefox development anyway). Mozilla sees this as a problem and has been actively looking for ways to diversify its revenue streams in the past years (go read any of their past financial statements to see them explicitly categorize their over-reliance on search engine revenue as a potential threat to the company), which has led to things like FirefoxOS (in the hope that telecoms would toss some cash Mozilla's way) and the "suggested sites" on the New Tab page. This why I find it extremely unlikely that someone "cut a deal", because Mozilla would want people to know that they're succeeding at the task of finding alternate revenue streams.