Slashdot Mirror


It's Not the 15th Birthday of Linux

Glyn Moody writes "There's been a spate of celebrations of Linux's 15th birthday recently. What they're really marking is the 15th anniversary of version 1.0. But do version numbers matter for free software? The 'release early, release often' approach means there's generally little difference between version 0.99.14z, say, and version 1.0. In fact, drawing attention to such anniversaries is misguided, because it gives the impression that free software is created in the same way as traditional proprietary code, working towards a predetermined end-point according to a top-down plan. So how should we be choosing and celebrating free software's past achievements?"

20 of 261 comments (clear)

  1. Yeah Yeah Yeah by Lord+Kano · · Score: 5, Insightful

    Free software isn't developed according to the same models as proprietary software. We get that. It's just backwards to complain about how people take the time to celebrate the achievements of free software developers.

    LK

    --
    "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
  2. "Release early, release often" by Blakey+Rat · · Score: 4, Insightful

    I've always thought "release early, release often" is a terrible idea. That just means all your end-users will see the crap you're working on before you do the testing, and get a bad impression of your software right from the get-go. It makes sense to do that *after* you hit 1.0 and have a pretty clean product, but why would you want people forming their first impression of your software from untested development releases?

    1. Re:"Release early, release often" by zappepcs · · Score: 3, Insightful

      Because waiting YEARS for Vista sucked, and the end product sucked even harder after all that wait... that's why.

    2. Re:"Release early, release often" by OneSmartFellow · · Score: 2, Insightful

      The OP obviosuly wishes more software projects were like Vista.

      You know, announced before it was begun, released before it was stable, out of date before it was fixed, over-priced, under-supported, and just plain crap !

      Me, I'll choose evolution over revolution because it seems to work well for other complex systems too.

    3. Re:"Release early, release often" by Blakey+Rat · · Score: 2, Insightful

      At least it worked. That's better than most "released early" open source software I've tried.

    4. Re:"Release early, release often" by olddotter · · Score: 4, Insightful

      I personally would not argue with Linus on how to run a successful open source project. You, of course, can do what you want.

    5. Re:"Release early, release often" by Anonymous Coward · · Score: 2, Insightful

      >release early, release often" is a terrible idea.

      Err. Not to the non-computer-savvy end users.

      That's why the first release is 0.1. If you give a 0.1 release to a non-computer-savvy end user, you're insane. On the other hand, that early is the best time for other computer-savvy users (=programmers) to see it and still be able to change fundamental stuff.

      >That just means all your end-users will see the crap you're working on before you do the testing, and get a bad impression of your software right from the get-go.

      Of your 0.1 software? I guess it depends on their expectation, but they shouldn't even see it, much less have opinions about something that most probably doesn't even compile on some machines, much less work in some finished for.

      >It makes sense to do that *after* you hit 1.0 and have a pretty clean product,

      No, please, no. There's no way you can change any big thing of it without having to essentially make it 2.0 and wait half a year or more until the mess finally compiles again. Just release what you have when you have it.

      >but why would you want people forming their first impression of your software from untested development releases?

      So that they can participate in your development.

  3. Ummm yes... by MikeRT · · Score: 3, Insightful

    But do version numbers matter for free software?

    Version numbers matter to the average user. If you have a product that takes years to break version 1.0, the uninitiated will wonder why it took you so long to "get it working." This question is another example of how many FOSS developers and advocates don't understand the basic psychology of the masses.

    1. Re:Ummm yes... by Directrix1 · · Score: 3, Insightful

      Right... the masses... Lets perform a psychology "experiment" here. Ask any non-geek what version number of any piece of software they are running. Hell, ask them for the name of that software. Most cannot answer either. Generally, "the masses" only know a couple things "this is my internet", "this is how I type stuff", "this is how I email", etc.

      --
      Occam's razor is the blind faith in the natural selection of least resistance and in universal oversimplification. -- EF
  4. Usenet post? by Max+Romantschuk · · Score: 5, Insightful

    Isn't the most logical Linux birthday when Linus first posted his code for others to improve upon? If memory serves me correctly it was a Usenet post?

    --
    .: Max Romantschuk :: http://max.romantschuk.fi/
  5. In Korea by psnyder · · Score: 4, Insightful
    In Korea, you are 1 year old the minute you are born. In most other countries you are considered 0 years old until your first birthday.
    It's a different way of counting.

    You can consider software (such as Linux) beginning as the first line of code is written, or when the idea was first conceived, or when it was first on the internet, etc. Most people consider version 1.0 to be more of the official "birth" of software.
    It's a different way of counting.



    Both are correct when thinking of them from different perspectives. To understand this requires mental flexibility in your ways of thinking.

    As a further illustration:
    The argument presented in both the article and summary:

    there's generally little difference between version 0.99.14z, say, and version 1.0

    There's generally little difference between a fetus the day before it's born and the day after it's born. But culture generally starts counting after it's born and not at conception. Computer culture often starts counting at v1.0

  6. Remember the Millenium by DynaSoar · · Score: 2, Insightful

    Despite the quite correct statement by a few people that the millenium changed Jan 1 2001, the vast majority of people ignored that and celebrated the arrival of 2000 as the new millenium. No matter how right you are about Linux's age etc., the vast majority will completely fail to notice you and your dogmatic assertions, and will enjoy themselves in spite of you.

    --
    "I may be synthetic, but I'm not stupid." -- Bishop 341-B
  7. I think you're analyzing it too much by HikingStick · · Score: 3, Insightful

    If you think about birthdays among people, they don't simply grow on the date of their birth. They are constantly growing and learning and developing. Birthdays are commemmorative events that celebrate when someone joined a specific family (or the human family in general). That's really not that different than what you described regarding open sources software.

    Perhaps "anniversary" would be a better term. A marriage rarely has its beginnings at the altar or in front of the justice of the peace. The persons involved typically began interacting with each other, learning, and growing together before the date of the actual ceremony, yet we celebrate their anniversary on the date they made their public vows in front of witnesses. I can see a parallel between pre-release and beta editions culminating with a public 1.0 release (or whatever the given name or number of a product may be). I don't see it as a disservice to the open source community to mark such milestones. In fact, if they were to describe the development process similarly to how I described it here--as an ongoing, growing, developing thing--it might actually mean more to some people.

    In any case, observing a birthday or anniversary holds powerful meaning regardless of the context (human or inanimate): it means the person or the thing survived the test of time. That's why so many businesses are quick to proclaim "...since 1933", "...established 2006", or similar sentiments that convey age. They understand that people tend to trust established brands, thinking (consciously or subconsciously), "if they've been around that long, they can't be too bad," or, "if they've been around that long, there's a good chance they'll still be around in a few years if I need to exercise my warranty rights."

    So, for me, I'll say happy anniversary Linux. You've had a good start. I'm looking forward to what the next 50 years will bring.

    --
    I use irony whenever I can, but my shirts are still wrinkled...
  8. A lack of planning by squoozer · · Score: 2, Insightful

    A lack of planning and having defined goals is not the same as working in a new and different way. If a survey of the most successful open source project was to be done I would put money on every single one having a strong plan and good leadership. Fair enough that leadership might be technical rather than the typical management type but it would be there.

    This whole "we won't call it 1.0 till it does everything perfectly" thinking smacks of childishness to me. Set some goals and publish them along with version numbers so that people know what to expect when. FFmpeg is a prime example of a project that should be 5.0 not 0.5. It's a mature, feature rich and stable lump of code that is in widespread use. Give it a version number that reflect that.

    --
    I used to have a better sig but it broke.
  9. What's so special? by digitig · · Score: 5, Insightful

    What's so special about the 0xFth anniversary anyway? Shouldn't we be waiting for next year and celebrating the 0x10th anniversary?

    --
    Quidnam Latine loqui modo coepi?
  10. Free:Proprietary::Incremental:Waterfall -- FALSE by browncs · · Score: 2, Insightful

    The two actually have nothing to do with each other. Many "proprietary" software projects are done in an incremental, release-often mode. Many "free" software projects are done in a waterfall, plan-design-code-test-release mode.

    By promulgating this myth, you are actually doing free software a big disservice, by limiting it to a certain style of development.

    Go away, ponder, then come back and repent.

  11. a proper linux milestone... by steak · · Score: 3, Insightful

    the first time a slacker sneered derisively at a red hat user. a.k.a. the beginning of the distro wars.

  12. Re:Who cares? by Probie · · Score: 2, Insightful

    Not our saviour, your saviour. But I was trying not to go down the path of denouncing my faith, to save from hurting your feeling. But as we are now currently on said path, and as many people have pointed out; Christmas was a pagan festival that was adopted by Christians. Santa stole a holiday of Christians....who stole a holiday.

    --
    Who? Who is but the form following the function of what and what I am is a man in a mask.
  13. Re:Who cares? by khellendros1984 · · Score: 3, Insightful

    Why bother being offended by what someone else says? I believe in the divinity of Christ, and the things I say will reflect that. Others believe that he didn't exist, or was just a man, or a charlatan, or a lunatic....regardless, I don't have evidence either way. Just belief. Why should someone be upset that: 1. different people believe different things and 2. people act upon the things they believe?

    --
    It is pitch black. You are likely to be eaten by a grue.
  14. Re:Who cares? by ocularDeathRay · · Score: 2, Insightful

    I celebrate Linux everyday of all the years.

    --
    Obama is a twitter sock puppet