Ruby in the VM: RubyCLR / JRuby Competing with your RSS feed
Oct 25

The freedom of limiting features

Tech Add comments

I was in Douglas Crockford’s JavaScript talk at The Ajax Experience and he said something that resonated a lot.

As a youthful journeyman programmer he used to learn every feature of a language/platform and tried to use everyone on a daily basis.

Now he has a subset of features that he relies on, and he sticks to those.

I have found myself doing the same thing. It makes learning new languages and platforms a lot easier too, as I do not feel the pressure to learn every nuance on day one.

Did I really need to learn about “class <<self;” on day one of Rubyland to be productive in Ruby? No.

I think it is important to learn how to work in a given language, and it isn’t that you should get stuck in your ways and try to write JavaScript as though it is Java (the opposite to what Douglas wants).

Learn the ways, do not feel the pressure to learn every library and feature, and get really good at your subset.

2 Responses to “The freedom of limiting features”

  1. Nathan Lee Says:

    I’m with you on this one.. Once you’ve got your toolkit of developer stuff and can do everything you need the rest is just fluff really.

    Take java and the “new” (ish) language features: are they really necessary?
    Meh.. Not really, survived X years and Y projects without ‘em.

    I guess this could be holding back programming as a whole as you have a mass of developers that depend on a mass of things (language features, APIs, libraries etc) and who insist a new one have all those things before it is as good as the old one..
    So to that end you have C/C++ people wanting stuff in java and c#, and if everything was accomodated for you’d have a massive bloat in syntax/APIs etc.

    Take the axe to some of this extra rubbish I say!

  2. Douglas Crockford Says:

    Just to be clear: I am not advocating ignorance. Lordy, there is already way too much of that in the Ajax world, and on the web in general. I am strongly in favor of people knowing what they’re doing.

    Buried deep inside of JavaScript is a beautiful little language. It is what is left after stripping away all of the design errors and weak inspirations.

    When I teach JavaScript, I include the bad features, so that by contrast students can recognize the good ones.

Leave a Reply

Spam is a pain, I am sorry to have to do this to you, but can you answer the question below?

Q: What is the number before 3? (just put in the digit)