The Gut Factor

written by Tobie on May 11th, 2007 @ 08:51 PM

Seen on project.ioni.st today:

The feeling I get when programming is at least as important as other factors when selecting a language.

Chad Fowler

That’s what I refer to as the gut factor. And which is what made me stick with Prototype when no documentation was available, updates were scarce, and people were migrating en masse to jQuery and YUI.

Looking back, that was one of the wisest decisions I made: I learnt way more about JavaScript helping out with the documentation and joining the Core Team than I would have otherwise.

What about you. What factors pushed you to adopt the language, framework, or library that your are using today ?

Comments

  • kangax
    kangax says:

    I stumbled upon The JavaScript Library World Cup article @ Sitepoint some time ago and made a decision to go with Prototype. I love prototype. It’s amazing how much one can learn just looking through its source.

    Few things that I’m missing are: publisher-observer implementation, cookies helpers, better mouse button detection and, of course, onDomReady or similar support.

    On the other hand, “keep-your-core-small” approach that prototype sticks to can not be underestimated. After all, it never hurts to include couple of third party scripts :)

    Fri, May 11 at 23:04 PM

  • Kroc Camen
    Kroc Camen says:

    Gosh, just how I felt. I started a project using Prototype/Scriptaculous and a slew of other scripts, and over time the growth of Prototype has allowed me to reduce my code and dependencies further and further.

    When I heard about jQuery, I was in two minds– sure it’s documented and smaller, but I stuck to Prototype based on the same gut feeling. My only gripe is that Scriptaculous is in a state as awful as Prototype was in before 1.5. It’s mostly undocumented, bloated and very buggy.

    I only hope that Scriptaculous gets documented exactly the same as Prototype, and the two libraries come together much closer. I am stuck on Prototype 1.5.0 because 1.5.1+ does not work fully with Scriptaculous SVN. http://dev.rubyonrails.org/ticket/7809

    I think I want to get into contributing to Prototype and Scriptaculous, but it does not help that the team insists on not linting, nor commenting any code. Please see my own project (click my comment name) for an example of how it’s done well. Thorough commenting /explaining / documentation throughout that is stripped out by the build process, so there’s no bloat to the end user.

    Sat, May 12 at 18:32 PM

  • Kevin Miller
    Kevin Miller says:

    I was in the same boat. Prototype just seemed to make sense, even if I had to hunt for the docs (on a dozen different sites). I am glad I stuck with it.

    Kevin

    Tue, May 15 at 12:28 PM

Comments are closed