Skip to main content

Ruby isn't going to fracture, and "enterprise" is not synonymous with "static"

I don't follow Ruby development too closely (most of the info on it is still in Japanese, after all), but the US RubyConf was held recently so there's been an unusual number of English posts on Ruby, among them David Pollack's The Impending Ruby Fracture.

David's article seems to consist of these points:

  1. Matz is uninterested in adding static bondage & discipline features to Ruby (true, as far as I know)
  2. "Enterprise" users won't be satisfied without said features (more on this below)
  3. There are a lot of Ruby runtimes out there right now (the most interesting part of the article)
  4. Therefore some Enterprise will co-opt one of the runtimes to fork Ruby and add the B&D features (wtf?)

Summarized this way it looks faintly ridiculous, and yet nobody over on the programming reddit has called this out. Maybe I'm taking excessive liberties with David's article, but I don't think I am.

The possibility of forking is part of what makes open source wonderful. The actual cost of a fork is astronomically high; almost nobody has made it work. For every X.org there are dozens of failures and probably far more where the would-be forkers realized that however bad the situation was, actually forking would be worse.

Now, in the absence of strong leadership, what you can have happening to a language is de facto forking, like what you have with Lisp -- the Common Lisp standard is old, so the various Lisp implementations have gone their separate ways to various degrees and portability between them is pretty dicey. But the Ruby community seems to be pretty content with the job Matz is doing so I don't see this happening.

As a motivation to assume the huge costs of forking, David submits... "interfaces or some other optional typing mechanism?" Excuse me. Even though some intelligent language designers have flirted with ideas along those lines, that's not something that's going to get refugees from Java to rally around your banner for a fork.

I also have to take issue with David's characterization of this as features that "appeal to enterprise customers." While it may be true that B&D languages are currently popular with large corporations, other large corporations recognize the advantages of dynamic languages. Corporations aren't stupid; they're just very conservative, for the most part. In 10 years you'll see more Python and Ruby in the enterprise, just as Java and C# are replacing COBOL and C++ now.

Comments

Anonymous said…
You didn't say what I thought you were going to.

Why would corporations want B&D Ruby anyway? Don't they have Java anyway?
Jonathan Ellis said…
That is also a good point. :)

Popular posts from this blog

Why schema definition belongs in the database

Earlier, I wrote about how ORM developers shouldn't try to re-invent SQL . It doesn't need to be done, and you're not likely to end up with an actual improvement. SQL may be designed by committee, but it's also been refined from thousands if not millions of man-years of database experience. The same applies to DDL. (Data Definition Langage -- the part of the SQL standard that deals with CREATE and ALTER.) Unfortunately, a number of Python ORMs are trying to replace DDL with a homegrown Python API. This is a Bad Thing. There are at least four reasons why: Standards compliance Completeness Maintainability Beauty Standards compliance SQL DDL is a standard. That means if you want something more sophisticated than Emacs, you can choose any of half a dozen modeling tools like ERwin or ER/Studio to generate and edit your DDL. The Python data definition APIs, by contrast, aren't even compatibile with other Python tools. You can't take a table definition

Python at Mozy.com

At my day job, I write code for a company called Berkeley Data Systems. (They found me through this blog, actually. It's been a good place to work.) Our first product is free online backup at mozy.com . Our second beta release was yesterday; the obvious problems have been fixed, so I feel reasonably good about blogging about it. Our back end, which is the most algorithmically complex part -- as opposed to fighting-Microsoft-APIs complex, as we have to in our desktop client -- is 90% in python with one C extension for speed. We (well, they, since I wasn't at the company at that point) initially chose Python for speed of development, and it's definitely fulfilled that expectation. (It's also lived up to its reputation for readability, in that the Python code has had 3 different developers -- in serial -- with very quick ramp-ups in each case. Python's succinctness and and one-obvious-way-to-do-it philosophy played a big part in this.) If you try it out, pleas

A review of 6 Python IDEs

(March 2006: you may also be interested the updated review I did for PyCon -- http://spyced.blogspot.com/2006/02/pycon-python-ide-review.html .) For September's meeting, the Utah Python User Group hosted an IDE shootout. 5 presenters reviewed 6 IDEs: PyDev 0.9.8.1 Eric3 3.7.1 Boa Constructor 0.4.4 BlackAdder 1.1 Komodo 3.1 Wing IDE 2.0.3 (The windows version was tested for all but Eric3, which was tested on Linux. Eric3 is based on Qt, which basically means you can't run it on Windows unless you've shelled out $$$ for a commerical Qt license, since there is no GPL version of Qt for Windows. Yes, there's Qt Free , but that's not exactly production-ready software.) Perhaps the most notable IDEs not included are SPE and DrPython. Alas, nobody had time to review these, but if you're looking for a free IDE perhaps you should include these in your search, because PyDev was the only one of the 3 free ones that we'd consider using. And if you aren