Apparently (II) ...
Joined: May 2001
Posts: 93,305
Likes: 820
From: Nowhere
Originally Posted by Chazmo,Dec 1 2004, 10:01 AM
Apparently, I'm a dinosaur and I'm having trouble grok'ing how the open source community works.
1. 3 people decide to write a program. The write it, and share the source code on their site.
2. 17 people try it and like it, and point out bugs; they are promptly fixed by the 3 energetic programmers.
3. 91 people try the bug fixed version, point out bugs the first 17 missed, and suggest new features; the 17 bug testers deny the prescence of a bug and insist the features aren't needed; the 3 tiring programmers add/fix them anyway.
4. 341 people go on /. proclaiming how great the new program is; 42 people who have never actually used Linux/UNIX point out that the 341 people are bound to the cause of OSS rather than using good software.
5. 11912 people see the /. flame war and download the source, crashing the server; 11896 of them are perfectly content with it, but the other 16 go on /. and flame the previous 341 for ignoring bugs and missing features.
6. 340 of the flamed go on /. and lecture the 16 flamers on how valuable the tool is, and how great open source software is, and that if they really want to criticize they should offer to help or write their own; the other 1 offers to help the 3 now-frustrated programmers.
7. Steps 3 through 6 are repeated for many months, and sometimes years.
8. Eventually the original 3 are gone, scope creep has occured, and the program functions mildly better than the bloatware sold by M$ 3 years earlier.
Thread Starter
Joined: Jun 2002
Posts: 42,315
Likes: 45
From: Central Massachusetts
Originally Posted by WestSideBilly,Dec 1 2004, 01:02 PM
Quite simple:
1. 3 people decide to write a program. The write it, and share the source code on their site.
2. 17 people try it and like it, and point out bugs; they are promptly fixed by the 3 energetic programmers.
3. 91 people try the bug fixed version, point out bugs the first 17 missed, and suggest new features; the 17 bug testers deny the prescence of a bug and insist the features aren't needed; the 3 tiring programmers add/fix them anyway.
4. 341 people go on /. proclaiming how great the new program is; 42 people who have never actually used Linux/UNIX point out that the 341 people are bound to the cause of OSS rather than using good software.
5. 11912 people see the /. flame war and download the source, crashing the server; 11896 of them are perfectly content with it, but the other 16 go on /. and flame the previous 341 for ignoring bugs and missing features.
6. 340 of the flamed go on /. and lecture the 16 flamers on how valuable the tool is, and how great open source software is, and that if they really want to criticize they should offer to help or write their own; the other 1 offers to help the 3 now-frustrated programmers.
7. Steps 3 through 6 are repeated for many months, and sometimes years.
8. Eventually the original 3 are gone, scope creep has occured, and the program functions mildly better than the bloatware sold by M$ 3 years earlier.
1. 3 people decide to write a program. The write it, and share the source code on their site.
2. 17 people try it and like it, and point out bugs; they are promptly fixed by the 3 energetic programmers.
3. 91 people try the bug fixed version, point out bugs the first 17 missed, and suggest new features; the 17 bug testers deny the prescence of a bug and insist the features aren't needed; the 3 tiring programmers add/fix them anyway.
4. 341 people go on /. proclaiming how great the new program is; 42 people who have never actually used Linux/UNIX point out that the 341 people are bound to the cause of OSS rather than using good software.
5. 11912 people see the /. flame war and download the source, crashing the server; 11896 of them are perfectly content with it, but the other 16 go on /. and flame the previous 341 for ignoring bugs and missing features.
6. 340 of the flamed go on /. and lecture the 16 flamers on how valuable the tool is, and how great open source software is, and that if they really want to criticize they should offer to help or write their own; the other 1 offers to help the 3 now-frustrated programmers.
7. Steps 3 through 6 are repeated for many months, and sometimes years.
8. Eventually the original 3 are gone, scope creep has occured, and the program functions mildly better than the bloatware sold by M$ 3 years earlier.
Nice, Jeff. I like your perspective.
Thread Starter
Joined: Jun 2002
Posts: 42,315
Likes: 45
From: Central Massachusetts
Jeff, my Linux buddies are lovin' this... They say you missed some steps:
-------------
9. Some of the original three, now distraught about the direction of the original work, fork the code from some previous release and head off in their own new direction.
10. Linux distributors have to start providing both packages and configuration tools for both, even though they are mutually incompatible.
11. /. flame wars over which implementation is better.
12. In the end, one of them is doomed because it requires a kernel change that Linus won't accept because it will negatively impact Linux in some of those famous Linux/Windows web server comparison tests.
-------------
9. Some of the original three, now distraught about the direction of the original work, fork the code from some previous release and head off in their own new direction.
10. Linux distributors have to start providing both packages and configuration tools for both, even though they are mutually incompatible.
11. /. flame wars over which implementation is better.
12. In the end, one of them is doomed because it requires a kernel change that Linus won't accept because it will negatively impact Linux in some of those famous Linux/Windows web server comparison tests.
Joined: May 2001
Posts: 93,305
Likes: 820
From: Nowhere
Originally Posted by Chazmo,Dec 1 2004, 05:45 PM
Jeff, my Linux buddies are lovin' this... They say you missed some steps:
-------------
9. Some of the original three, now distraught about the direction of the original work, fork the code from some previous release and head off in their own new direction.
10. Linux distributors have to start providing both packages and configuration tools for both, even though they are mutually incompatible.
11. /. flame wars over which implementation is better.
12. In the end, one of them is doomed because it requires a kernel change that Linus won't accept because it will negatively impact Linux in some of those famous Linux/Windows web server comparison tests.
-------------
9. Some of the original three, now distraught about the direction of the original work, fork the code from some previous release and head off in their own new direction.
10. Linux distributors have to start providing both packages and configuration tools for both, even though they are mutually incompatible.
11. /. flame wars over which implementation is better.
12. In the end, one of them is doomed because it requires a kernel change that Linus won't accept because it will negatively impact Linux in some of those famous Linux/Windows web server comparison tests.
Is this going to show up on /. ?
Registered User
Joined: Jun 2004
Posts: 38,617
Likes: 1
Originally Posted by WestSideBilly,Dec 1 2004, 03:03 PM
Is this going to show up on /. ?
