Rhino VS BeanEven if I'm the NoScript guy, I write a lot of JavaScript all the day. As you probably know, even the JavaScript Annihilator is mostly written in JavaScript. Like Crock, I love the language, despite its current browser-bound shortcomings.

So far, my favourite editor for JS coding has been JEdit with its JavaScript plugin, providing syntax highlighting (of course!), on the fly syntax checking via Rhino and optional code completion with configurable scopes, including Mozilla "chrome window" and XPCOM.

But today I've watched a presentation of the new NetBeans 6.1 JavaScript capabilities, and I'm impressed.
Dynamic type guessing, browser-specific contextual help and DOM-aware AJAX library support (John, guess which they show in their demo?) may be really worth the switch.

6 Responses to “NetBeans Groks JavaScript”

  1. #1 Rafael "g0dkar" Lins says:

    Netbeans' JavaScript support is quite impressive. I'll surely give it a try. Thanks for sharing this with us =)

    And BTW, great image... Bean vs. Rhino, hehe =P

  2. #2 funtomas says:

    One word: wow!

    Well, a few more: Seems to me, Steve's complaint (http://steve-yegge.blogspot.com/2008/05/dynamic-languages-strike-back.html) about lack of JS tools is no longer valid

  3. #3 davide ficano says:

    I'm a KomodoEdit guy :P
    KomodoEdit is open source and written using Mozilla Gecko
    It has a good JS/XPCOM/XUL support and last but not least startup is faster than NB ;)

  4. #4 Rey Bango says:

    jQuery is on fire. Thanks for the mention Giorgio.

    Rey - jQuery Team

  5. #5 Wired Earp says:

    I'm gonna leave a mention of the Eclipse Ajax Toolkit Framework around here. You can check out the features over at (http://www.eclipse.org/atf/features/index.php). I'm using an old version of the framework myself (because I have to make it work with certain antiquated Eclipse plugins) so I cannot compare it directly to NetBeans, but it has a built-in Rhino engine for much the same purposes. You also get a Mozilla instance embedded directly into the IDE with full script debugging, DOM inspector and httprequest monitoring. With these frameworks in direct competition, surely we're heading for a golden age of javascript authoring. But I'm gonna stick to Eclipse myself, in the belief that they will be first to pick up on JS2.0 support (as soon as Rhino can handle it).

  6. #6 tenest says:

    I've always used Aptana (an off-shoot of Eclipse) for my JS development, but after watching that demo, i am FLOORED. Thank you Giorgio for sharing.

Bad Behavior has blocked 3417 access attempts in the last 7 days.