The Pitfalls and Perks of Adopting a New Standard 87
Monta writes to tell us that IBM DeveloperWorks has an interesting article about the pros and cons of 'adopting a standard before it becomes one'. From the article: "Whether a standard will succeed and be widely adopted is ambiguous at first, regardless of who endorses it -- a major player or a fringe element. So if most people don't like to welcome the new guy, why would they put all their eggs in a standards basket when that basket might not exist tomorrow?"
Yeah... (Score:5, Funny)
Sticking to an old standard (Score:5, Funny)
I, for one, welcome the new guy!
Re:Yeah... (Score:4, Funny)
1. Wait for a good open standard to come out.
2. Embrace.
3. Extend incompatibly.
4. PROFIT!!!
The great thing about standards (Score:5, Funny)
lets see (Score:2, Funny)
Slashdot should adopt a standard.... (Score:3, Funny)
Exactly how does one... (Score:3, Funny)
Is that like going to McDonald's, ordering a Chicken Sandwich, and getting an Egg McMuffin?
The great thing about standards (Score:2, Funny)
Re:angling for those IBM ad dollars, eh? (Score:2, Funny)
Huh?
The article was not a reg req offering.
Whatever you're smokin', pass it 'round.
Re:Sticking to an old standard (Score:3, Funny)
Re:Once in a while, it works (Score:2, Funny)