It's Not the 15th Birthday of Linux 261
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?"
Who cares? (Score:5, Funny)
Re: (Score:2, Funny)
Re: (Score:2, Informative)
Re: (Score:3, Interesting)
Christmas is based on non-Christian traditions that were absorbed by Christianity because they could not get people to stop celebrating them.
Although that's true, you're glossing over a little history there. The church couldn't get the countryfolk to stop celebrating Saturnalia, Solistice, etc. so they simply scheduled a Christian service for the same time, and anyone who didn't show up was subject to sanctions (note the root of that word, eh?) up to and including being burned at the stake as a pagan idolater.
Hahahaha! My captcha is "oppress"! Jung wins again!
Re: (Score:2, Interesting)
Slight misrepresentation there. "They" just the Emperor Constantine, and any sanctions would have been for insurrection or sedition, not for paganism. After all, he's the one, along with Licinius, who signed the Edict of Milan, guaranteeing religious (though apparently not atheistic) freedom across the empire -- and anyway, the pagans were having a party then, as required.
By the way, your etymology of "sanction" seems to be back to front. It's more likely that the meaning of "decree" led to the ecclesiastic
Re: (Score:3, Interesting)
Re: (Score:2)
Re: (Score:2)
It's not that people couldn't be be stopped, it's that there's no good reason to stop.
One year, you have a party in honor of the god(s) you believe in. During the year, you come to a new faith. When it's time for the annual party, unless there is something about it that's explicitly against the teachings of your new religion, why not have it like always, but instead of honoring the god(s) you used to believe in, do it in honor of the god(s) you believe in now?
There are piles of holidays like this, all
Re: (Score:2)
From my point of view I expected him to say "I celebrate Christmas but I don't believe in Jesus", but he said Santa. A lot of people would associate Christmas with Jesus Christ before Santa (the clue being in the name of the celebration). Maybe that wasn't the joke, but I found it funny..
Re: (Score:2)
My apologies, miss. I actually thought saying Santa was more controversial, as I could imagine all the Christians getting upset at someone claiming Santa to be the most important thing to believe in when it comes to Christmas ;) I would have been a little miffed at it a couple of years ago when I believed Jesus to be the son of god anyways :P Still, it gave me some amusement :)
Re:Who cares? (Score:4, Insightful)
Re: (Score:2, Funny)
'So how should we be choosing and celebrating free software's past achievements?'
Well, there are enough projects so that, like saints' days, there is something to celebrate every day. For, celebration involves tasty alcoholic beverages and comfy women (well, woman really; my wife).
Re:Who cares? (Score:5, Funny)
For, celebration involves tasty alcoholic beverages and comfy women (well, woman really; my wife).
Wow, so good of you to offer to share her around! Are you sure she'll be up for it?
Re:Who cares? (Score:5, Funny)
You better believe in Santa or the Coca-Cola guys are gonna come to your house and make you believe.
Re: (Score:2)
Yeah what's up with that ? I mean, I could imagine that if you lived in Australia, then associating a midsummer's feast with a cool beverage would not be so strange, but Christmas in the northern hemisphere ? What completely retarded marketing twat thought that up ?!
Re: (Score:2)
The thought police are branching out these days - now they like to censor feelings too.
I'm okay with it though, as long as they keep their hands out of my pants.
Re: (Score:2)
If you can't feel anything, how would you know their hands are in your pants?
Re: (Score:2)
I was referring more to emotional feelings/the-"heart", which could also be linked to thoughts/the-brain. In fact all of human experience kind of has to be experienced through thoughts or at least the brain - but that spoils the joke somewhat.
In addition there is the fact that I know that having someone's hands in my pants is fun, so I probably wouldn't object either way >_>
Re: (Score:2)
I'll send Eric Raymond and Richard Stallman right over!
Re: (Score:2)
Jesus Christ!
Re: (Score:3, Insightful)
Re: (Score:2, Insightful)
Yeah Yeah Yeah (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
Re: (Score:2, Funny)
*dances*
*dances badly but with passion*
Re:Yeah Yeah Yeah (Score:5, Informative)
i'm going to become rich and famous after i invent a device that allows you to stab people in the face over the internet [bash.org]
"Release early, release often" (Score:5, 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?
Re:"Release early, release often" (Score:4, Insightful)
Because waiting YEARS for Vista sucked, and the end product sucked even harder after all that wait... that's why.
Re: (Score:3, Insightful)
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.
Re: (Score:3, Insightful)
At least it worked. That's better than most "released early" open source software I've tried.
Re: (Score:3, Informative)
Parent item is an uninformed Microsoft troll.
"Release early, release often" doesn't mean you push non-working software into production channels.
The point of "release early, release often" is that a wide and open circle of potential users can become collaborators in the development process.
That doesn't mean they write code or even follow good formal test practices. Even without technical skills, users can contribute materially to the development of a well-run open-source project.
If you won't want to sign up
Re:"Release early, release often" (Score:5, Interesting)
Release early, release often, release statements of current functionality. Seriously, no non-geek is going to be installing software that isn't test by some bff geek anyway. So release early and often so the geeks can help guide its direction and give feedback.
Re:"Release early, release often" (Score:5, Funny)
I've always thought "release early, release often" is a terrible idea.
My wife tells me the same thing.
Re: (Score:3, Funny)
? Strange. Your wife tells me something completely different.
Re: (Score:2, Funny)
Re: (Score:2)
I don't seem to remember many people complaining about Mozilla Phoenix/Firebird, not-so-many years ago when it hadn't even reached 1.0 ...
Re:"Release early, release often" (Score:5, Insightful)
Re: (Score:2)
How exactly do you plan on having an open-source project if you don't release it?
Re: (Score:2)
The point about "release early, release often" is that you do it to people who are aware that it is not the final version, and who will give you constructive feedback....
Ordinary users who will at best say "It didn't work" are not your target audience....they are the people who you give v1.01 Stable release to ....
The reason Vista is hated so much is it's usability, which beta releases should have found and corrected, but the Beta testers seemed to all be people who didn't complain enough?
Re: (Score:2)
The people seeing these fast releases aren't the end-users, but rather people that will be actively involved in the project and contributing back (coding, testing, etc.). This creates a fast feedback cycle. It's the core of running the development "bazaar", if you will.
After OpenBSD opened up their code repositories for anyone to read, everyone else started doing it. This pushed even further, so that anyone could access the exact state of a project at any time.
Re: (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 fro
Re: (Score:2)
Well the case of Birthday for things that were note born is always a fuzzy idea.
Just like the Abortion debate of when does human life begin.
Conception when you just a couple of cells, or in terms of software when you started coding
1st trimester when it is starting to grow and become more then a bunch of cells however indistinguishable for all other vertebrates. or in terms of code, it doesn't work but you got the data layouts sets and some proof of concepts sections working.
2nt trimester When Human disting
Re:"Release early, release often" (Score:5, Funny)
well, the point is to get people to test it so you can know if it's carp or not
Damn straight. I always want to know if there's anything fishy about the software I use.
Re:"Release early, release often" (Score:5, Funny)
Re: (Score:3, Funny)
You don't want to flounder if an unscalable version comes down the pike, though.
Re: (Score:3, Funny)
Not so hasty. There are some non-obvious benefits to fishy software.
Right now I'm working on Fishix, a *nix based OS that eats it's own bugs!
Which will be real handy. Since I don't know how to program, I'm expecting a lot of bugs!
Linux' Birthday is ... (Score:5, Funny)
Here's one that will last forever... (Score:4, Funny)
Re: (Score:2, Funny)
Comment removed (Score:4, Insightful)
Re:Ummm yes... (Score:4, 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.
Re: (Score:2)
So, if I search for a password manager tool and find one that's at version 0.35d, I'm wondering: "what is missing from this software that would actually make it a password manager?" Maybe there is no encryption of the datafiles? Maybe the developer still wants to include a print report function but hasn't had time yet? Maybe there is a occasional corruption bug that messes up the datafiles 1 time out of 1000000 saves?
Or maybe nothing is missing at all.
Re: (Score:2)
Which means the programmer doesn't have any confidence in his/her product to declare it finished.
So why would I want to use it?
Re: (Score:2)
Which means the programmer doesn't have any confidence in his/her product to declare it finished.
The person said "minimally feature complete" not "finished". They aren't the same.
So why would I want to use it?
Because it works?
Re: (Score:2)
Or maybe nothing is missing at all.
Then the project lead should officially tag it as '1.0' to let the world know that no essential functionality is missing.
Version numbers have meaning, or at least used to prior to 1995. If the developers have designated a release as version 0.35d, you'd be a fool to entrust it with any critical or sensitive information.
Usenet post? (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?
Re: (Score:2)
No I think I would stay at the version 1 release.
As after version 1.0 was released it was actually started to be used as a real OS for non-kernel developers. Other apps may be different. I have been using the text editor jed for nearly 15 years as well and it is still not version 1.0.
However Linux has a more sane Version Number system, so it is fair to use 1.0 for its birth date. Other systems not so much.
Re: (Score:2)
My company was running its corporate mailserver on a Slackware distro using kernel 0.9 something in 1993. Compiling your own kernel was compulsory in those days - I think Slackware came with a minimal kernel to get you bootstrapped.
Re: (Score:2)
Re:Usenet post? (Score:4, Funny)
Re: (Score:2, Informative)
Witch would be:
Aug 26 1991, 7:12 am, when Linus revealed his intentions [google.com]
or
Oct 5 1991, 4:53 pm, when he announced the availability of Linux [google.com].
Either way, Linux would 20 in two years time and 18 later this year.
Re:Usenet post? (Score:4, Funny)
That post is more akin to Linus announcing he was pregnant. I would regard the 1.0 release as the birth, with initial coding of the 0.x releases akin to baby showers and painting nurseries.
The conception, like most, was the result of a drunken night in front of a computer terminal, filled with unwise and hasty decisions. When Linus woke the next morning, with the most schocking hangover, he saw before him the beginnings of an x86 OS kernel, with drunken documentation and to do lists, and no memory of how any of it came to be on his hard drive. He took it from there.
I mean, no one honestly decides to write a kernel when they're sober, do they?
Re: (Score:2)
Honestly? (Score:2)
To be honest, I think that this might be part of the reason half the world is having trouble adopting to open source software. It's like a freshman trying to date a senior. GROW UP!
Major versions matter (Score:2)
As long as the developer still has the human trait of assigning meanings to numbers, any major version X will have a gravity that version X-1.9.Z does not. Barring minor versions that happen to match up to pi, prime numbers, fibonacci sequences, etc.
Consciously or subconsciously, someone is saying "what happens next is different", otherwise they'd just make it a point release, or pick a different versioning system.
2000 all over again (Score:5, Funny)
Re: (Score:2)
Re: (Score:2)
How? That's easy. Why? Because we can. (Score:5, Funny)
So how should we be choosing and celebrating free software's past achievements?"
Booze. Lots and lots of Booze. And strippers. Lots of strippers. And pie. Gotta have some pie.
Re: (Score:2)
In fact, forget the booze and the pie!
Whole numbers in versions = big deal (Score:2)
I've been using it longer than 15 years. (Score:4, Informative)
Re: (Score:2)
Ya, me too. I remember compiling those kernels on a 386DX40 (with math coprocessor! lol). I had 4 MB of RAM which cost more than $300 back then due to the shortages, what a ripoff (but necessary to play Doom). It took about 45 minutes to compile even though the source base was tiny compared to what it is now. I also ran X11 just fine even though the "minimum" RAM was 8 MB.
I don't have that computer any more but I still use the monitor in my server room and the 345 MB Maxtor HD from that machine still wo
A real milestone (Score:2)
Maybe Linus' birthday would be a clear cut milestone?
free as in speech or free as in love? (Score:3, Funny)
So how should we be choosing and celebrating free software's past achievements?"
Declare it must be 5-o'clock somewhere, start drinking.
Much older then 15 years. (Score:4, Funny)
We all know that Linux was made in 1979 [wikipedia.org].
[yes this is a joke post]
Might as well celebrate Windows 3.1 (Score:2)
Anyhow, the first usable releases, such as the one I started on: 0.96 came out a couple of years earlier
In Korea (Score:5, Insightful)
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
Re: (Score:2, Funny)
Re: (Score:3, Informative)
In Korea, you are 1 year old the minute you are born.
China too, but it might be better to translate it as "in your 1st year".
Re: (Score:2, Funny)
Remember the Millenium (Score:3, 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.
Thanks for pointing this out (Score:4, Funny)
I, for one, do not plan to attend the parade, now that I know it's all a misguided sham...
Unbirthday (Score:2)
I think you're analyzing it too much (Score:4, Insightful)
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.
Re: (Score:2)
I think you're analyzing it too much
Over analyzing on SLASHDOT? You're kidding.
(What we need is a roast)
Now, all of the 300 or so Linux users should get together to celebrate this anniversary of a rewrite of a clone of a rewrite of Multics.
Happy anniversary Linux, thank you for bringing much needed over complexity to mainstream computing!
15 years phooey!! (Score:2)
Typical open source response... (Score:2)
I love open source, I really do. But the proponents by and large tend to lack a sense of pragmatism or a sensitivity to psychology (which explains the terrible UIs of many open source programs).
Just pick a date and give people their freaking anniversary. It's not going to hurt anything and gives people a chance to have a little fun and acknowledge the progress of the project.
A lack of planning (Score:3, 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.
What's so special? (Score:5, Insightful)
Free:Proprietary::Incremental:Waterfall -- FALSE (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.
Self-Hosting (Score:2)
Wouldn't it be more like being born when Linux was first able to self-host?
a proper linux milestone... (Score:3, Insightful)
the first time a slacker sneered derisively at a red hat user. a.k.a. the beginning of the distro wars.
For Linux 1.0 was NOT the beginning (Score:3, Informative)
For Linux using the release of 1.0 was something that happened late. the .9 series was long lived and mature. I'd been using Linux for a long time before 1.0 was released.
In people years, Linux 1.0 was more like a high school graduation than a birth. It meant that Linux was mostly grown up,
For Linux we do have a very good and well defined "birthday". The day Linux posted on usnet. Use that.
Let's Celebrate! (Score:3, Funny)
Linux: 15 years of being 5 years away from taking over the desktop!
Re: (Score:2)
And, really, shouldn't we be celebrating the day the puppy was *conceived*?
Re: (Score:2)
Re: (Score:2)
I'm confused. Is this an insult to Linux or to Jews?
Re: (Score:2)
All birthdays are arbitrary.
Why do we celebrate our age from the time of exiting our mother's womb? Why not conception? And what is a year exactly? Calendar year, sidereal year, local time or standard Earth time? How about if I travelled faster and slower during the year, and relativity effects kick in? How do we know the dates are correct? Humanity's obsession with these things is fascinating, and I get caught in it myself sometimes, but then I stand back and realize it's all arbitrary.
Yet it is not meanin
Re: (Score:2)
"On this day, XX years ago, my parents had hot hot sex and I just wanted to thank them for it. Without that hot hot sex, done by my parents, I wouldn't be here today with all of you. With that image firmly in all of your minds, lets party!!!"
I'll stick with tradition here.
Re: (Score:2)
Well going by the v1.0 is the birth of a project, then Wine is very young
That is why there are no naked pictures of Wine on the Internet yet. Just give it time.