7 ms·
Well, nobody sent them a patch until two months ago, nobody added tests until a month ago, and nobody fixed the broken tests until yesterday. So the title shou
by jrockway 15y ago
Well, nobody sent them a patch until two months ago, nobody added tests until a month ago, and nobody fixed the broken tests until yesterday. So the title should be more like, "Firefox adds line numbers to view-source the day after someone implemented them correctly."
This is how Free Software projects work; people that want a feature implement it. It's great that you want something and it's possible that your desires will line up with those of someone who can easily implement them ("oh yeah, great idea, i want line numbers too"), but more often than not, the people with experience on some project are more interested in some deeper problem. If you're hacking on the JS JIT, line numbers just aren't important to you; you never "view source" in the browsers and may not even run the browser all that often. It's likely that your "extracurricular hacking" will be on something like a better test harness or better Emacs integration with your development workflow.
It is hard to go from being a user of software to a developer of that software, especially in this day and age of easily-downloadable TV shows, movies, and /b/ memes. That's why it takes 7.5 years to find someone interested in hacking on this feature, them getting themselves up to speed on Mozilla, and then finally implementing an acceptable patch. It would be nice if someone got paid to work on this sort of stuff, but users are comparing Firefox to its competition with things like Javascript benchmarks and WebGL conformance, not whether the browser has line numbers in view source. That's not to say they're not important, but rather very easy to deprioritize when the people that know how to implement that quickly also know how to implement "bigger wins" more quickly.
Ultimately, a free software project lacks feature X because you haven't added it yet. Remember that when you submit complainy titles to HN. Don't rely on someone else to make your life better because you're going to be pretty disappointed when you realize that you don't matter much to the world at large. Everyone else has other things to do too.
- moonchrome 15y ago>This is how Free Software projects work Isn't Mozilla a non-profit org with a hefty budget ? I guess it isn't unreasonable to expect improvements from the core team. Sure you can't demand them but I guess once you have a paid team working on the project you expect some polish, especially when it coincides with their goals of helping/enabling developers.
- jrockway 15y agoIt is, but think about it; all the developers that know how to fix this also know how to fix one of the other million bugs in Firefox. And those are probably more important "to developers" than this one. All bugs and features are important to someone; the reality is that there is an infinite amount of stuff to do that would be of great benefit to everyone, but only a finite (but perhaps large) number of people that are able to act on. The only way to act purely in your own self interest is to do something yourself; then you get one task and one person to implement it that you have full control over. Acting entitled doesn't get you anything other than the ability to stop giving Mozilla money and switching to Chrome. (But I'm guessing that 99% of people wanting Firefox features aren't giving Firefox any significant amount of money. A feature like this probably takes someone skillful 8 hours to implement. At $100/hr, which is a reasonable rate for an employee with overhead, you should be donating $800 to be entitled to a fix. And that's not even how donations work.) I'm saying that if this enhancement was truly important, it would have been done sooner. What people think is important and what is important are often very different. "Let the market decide," is my philosophy.
- alinajaf 15y agoI think your point is that if you want a feature implemented in an OS project, you should implement it yourself. In practice, we're web developers, and it's much easier to just pick up google chrome than it is to get set up with developing firefox, getting into the code and implementing the change. That being said, I'm seriously considering cowboying up and contributing to get the ruby tag implemented in firefox. This is not because I use Firefox myself, but my users do, and faking it with js/css is brittle as hell.
- zobzu 15y agoYou can do so, however, note that you still need acceptance for mainline. Obvious things such as line numbers, are obviously accepted once implemented properly. Note: the below comment is actually inaccurate, I though ruby tag was the language (as the author mentioned js as alternative). Keeping it for the comments discussing it, but keep in mind I was actually wrong. Things like a ruby tag might be more complicated than you'd think. You see, the main difference between Firefox and Chrome (yeah, it's not the UI! ;P) is ideology. Firefox folks believe in a standard and compatible web. Chrome folks believe in .. implement whatever we think is faster than what we have (or /flamebait hat on, whatever helps Google make money/adverts/lock-in users). Supporting ruby might fall in the "but it's not standard" "it splits the web" category. And that's be correct, in my opinion. So you might want to check on that before actually getting the code done, unless you plan to fork.
- jrockway 15y agoChrome folks believe in .. implement whatever helps Google make money/adverts/lock-in users. Citation needed.
- cytzol 15y agoWhile I can't provide a citation, I believe that the contrapositive is true: if it doesn't help Google, it's not going to be implemented. Right now, Google's interests are aligned with a standardised, compatible web, and when Google gets big enough, or greedy enough, it's going to take Chrome in its own direction. Opera still fares badly at Google's services, but they consider IE worth supporting.
- baddox 15y agoIt sounds like you're saying that the entity called "Firefox" shouldn't be blamed for aissing feature, because it's up to people to write the code. That's a strange definition of what "Firefox" is. I think Firefox is its community of developers, both those that work on the product full time and those that volunteer. A lack of such an obvious feature is in my eyes a problem with "Firefox."
- jamesaguilar 15y agoDepends on which Firefox you are talking about. If you're talking about "the community of people and organizations that develop the browser called Firefox," then your post is correct. On the other hand, if you are looking at Firefox from the perspective of a consumer deciding between browsers, then the complaint is valid, assuming line numbers are important to you. They are kind of basic, and the product has gone long without having them. > Ultimately, a free software project lacks feature X because you haven't added it yet. This is also true of proprietary projects. I can edit the machine code or clone it. This fact doesn't invalidate observations of behind-the-times features in proprietary projects. In OSS, the barrier to entry is lower, but still substantial. Likewise, it's reasonable for us, as consumers, to observe when OSS projects don't implement things we want. I don't hold them to different standards merely because I have been invited to spend my valuable hours working on them.
- jrockway 15y agoI guess I will boil my argument down to: it's not their fault it's bad, it's your fault you're using it. This applies equally to Free Software and proprietary software. "Don't like it? Don't use it." Your complaining isn't going to make the software better. Decide on a course of action that will resolve your complaints, and then act on it. Posting to HN, "look at those l4m3rz at Firefox not implementing my features! They suck!" does not count because the logical conclusion of this action does not lead to increased happiness (either yours, or the wider community). It's like a little kid complaining to his teacher, "Johnnie hit me!", the teacher asking Johnnie "Why'd you hit Bobby?", and Bobby saying "Because Johnnie hit me first". The end result is a couple of sore schoolkids and an irked teacher. As adults, we need not let our actions devolve this way. So, if this issue bothers you, you need to suck it up and stop using Firefox, or suck it up and implement the damn feature that you obviously care so deeply about. If you don't care about your feature enough to implement it, why should anyone else? Why are other people different from you? Because they've implemented features before? You expect free work from people that have given you a free product, simply because they have proven themselves willing to work for you for free before? Right, that make sense. The advantage that free software projects have over "don't like it, don't use it" is that any user can change the software and other users will be thankful for the time and effort you put in. That's what being an adult is like. Ultimately, all free software is based on altruism; people contribute because they want to. If you don't understand the concepts altruism or community and just want to take and complain, then you're not going to get any argument about how you should take ownership of issues that concern you.
- akkartik 15y agoPlease provide a criticism of open source software which you can't answer with "If you don't like it, fix it."[1] I wager you can't. If that's true, you're basically claiming that open source projects are immune to criticism[2]. [1] It's really, "If you don't like it, learn programming, then download the source code, then learn to build it, then learn to read it, then make your change, then build it, then use it, then champion getting it merged." [2] Complaint, whine, we can call it whatever you want. I'm a grown man secure in my whining. --- Do you really go hack on random large codebases at a moment's notice when something about them irks you? If so, please know that nobody else on the planet can do this without spending weeks of time (conservatively). It's utterly disingenuous to so ignore the fixed costs inherent in programming. --- Is this the same firefox that can afford to advertise in the NYTimes? How much of its development is really on a volunteer basis anymore? Let's decide once and for all whether this is a mature codebase that's encouraging us to use it for mission-critical work in the world. If it is, it's open to criticism (yes, even trivial criticism).
- Zev 15y agoDo you really go hack on random large codebases at a moment's notice when something about them irks you? If so, please know that nobody else on the planet can do this without spending weeks of time (conservatively). Yes. At least when the codebase is in a paradigm that I'm familiar with. Note: language is not important in exploring a codebase. I probably couldn't do this with, say, GHC. But, I bet I could with Clang or a js library, if I wanted. While I might not know my way around the codebase, I can certainly use grep to find where I need to go, or just ask someone on irc. In a few hours, I can at least find where I need to be, and be hacking. The end result might not be good enough to send in as a patch, but it'll certainly fulfill my needs. Sure, I have some skills that others don't. But, I'm not the only one who can do this, either.
- joeyh 15y agoIt's interesting to think that this might be a skill that we free software developers have to degrees that other developers don't. I generally think of this as "hacking".
- saturn 15y agoBy this logic, it is impossible to evaluate any open source project, because all that ends up being evaluated is the reviewer's personal failure to implement whatever qualities they were looking for.
- rimantas 15y ago> This is how Free Software projects work I'd argue that was the opposite how Firefox project worked when Blake Ross was still guiding it. Clear vision and direction, not passive wait for someone to submit something. Without this any project just becomes a mess of patches.
- jrockway 15y agoThat's simply not true. Maintainers exist to coordinate effort, not to do all the work themselves. A good example is GNU Emacs. There are two maintainers, but most of the code is written by other people. Even RMS' code doesn't amount to a particularly large percentage of Emacs anymore.