The Artima Developer Community
Sponsored Link

Ruby Buzz Forum
The Paradox of (Programming Language) Choice

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Daniel Berger

Posts: 1383
Nickname: djberg96
Registered: Sep, 2004

Daniel Berger is a Ruby Programmer who also dabbles in C and Perl
The Paradox of (Programming Language) Choice Posted: May 23, 2007 12:10 AM
Reply to this message Reply

This post originated from an RSS feed registered with Ruby Buzz by Daniel Berger.
Original Post: The Paradox of (Programming Language) Choice
Feed Title: Testing 1,2,3...
Feed URL: http://djberg96.livejournal.com/data/rss
Feed Description: A blog on Ruby and other stuff.
Latest Ruby Buzz Posts
Latest Ruby Buzz Posts by Daniel Berger
Latest Posts From Testing 1,2,3...

Advertisement
One of the slides Avi Bryant showed during his RailsConf talk bragged that Smalltalk had multiple commercial vendors.

Is that something to brag about? Frankly, I think it's one of the reasons (of several) that Smalltalk will never regain significant traction, assuming it ever really had any. Consider this thread where you've got Smalltalkers going after each other about incompatibility issues between different versions of Smalltalk.

Think about that for a moment. Now put yourself in the shoes of a PM who's trying to decide *which* version of Smalltalk to use. There are what, 12 versions of Smalltalk out there, each with various features? Forgetting for the moment that all but one are not free. And nothing but a bunch of Smalltalk programmers, each with their favorite flavor, to help you decide.

How does this scenario help a language in the long run?

It doesn't. The paradox of choice ends up working against it. It becomes marginalized. The PM opts for another language that only has one (primary) implementation. And probably a free one to boot.

Ruby is in a precarious position at the moment in this regard. Right now we've got MRI Ruby, JRuby and IronRuby. Life good because the latter two can solve deficiencies in the language that will make them better than MRI Ruby. Also, IronRuby will be targeted at a specific platform, so the choices now are easy.

But that may not last.

What happens when Ruby 2.0, JRuby, IronRuby, etc, all reach production worthiness?

Now put yourself in the shoes of a PM...

Read: The Paradox of (Programming Language) Choice

Topic: 7 Things You Can Do With Ruby Previous Topic   Next Topic Topic: hoe version 1.2.1 has been released!

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use