The Artima Developer Community
Sponsored Link

Java Community News
Three NetBeans Evangelists Discuss NetBeans 6.1 Beta

3 replies on 1 page. Most recent reply: Mar 20, 2008 6:04 AM by Bill Pyne

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 3 replies on 1 page
Frank Sommers

Posts: 2642
Nickname: fsommers
Registered: Jan, 2002

Three NetBeans Evangelists Discuss NetBeans 6.1 Beta Posted: Mar 19, 2008 5:37 PM
Reply to this message Reply
Summary
NetBeans is Sun's open-source, multi-language IDE. The latest release, a beta version of which was made available this week, includes support for JavaScript, Spring, Rails 2.0, and includes many performance improvements. In an interview with Artima, three NetBeans evangelists discuss these new features.
Advertisement

Sun released the 6.1 beta version of its open-source NetBeans IDE. In an interview with Artima, three NetBeans evangelists talk about the most important new features in the latest version of NetBeans:

Frank Sommers: Could you tell us about new JavaScript support in 6.1?

Brian Leonard: If you're familiar with what we've done with Ruby in 6.0—the code-editing features you expect from code completion for methods, dynamic type analysis, documentations online for the methods available on the various classes, and so on—all those features are now available for JavaScript, too.

One of the features I like especially is browser-compatibility checking. Assuming that you want to write JavaScript for all the four [major] browsers, if you start using a method that's not available on a particular browser, NetBeans shows you that with a drop-down list, highlighting the method in question with a strike-through. If that browser, or a particular version of that browser, is one that you don't care about, you can tell NetBeans that, and that will turn this checking off for that browser or browser version.

If you want to work with a JavaScript framework, you just add the JavaScript libraries to your project, and that's equivalent to adding a Java library to a Java project: the editor will become aware that that JavaScript file or library is available, and will provide all the editor features, such as code completion, for that library. For example, if you use script.aculo.us and then type effect, the editor will show you the various effects you can apply in that library.

In terms of refactoring JavaScript code, we don't have much of it in place yet, but I'd expect that that, too, will become similar to what we have for Ruby. At the moment, we offer the ability to rename variables, and later we will provide additional refactorings. The other big feature that we're missing in the Beta 6.1 is JavaScript debugging. My understanding is that that will be in the final version of 6.1.

Frank Sommers: There has been some talk about NetBeans supporting Python development as well. Is this already available in 6.1?

Gregg Sporar: The news is that two of the main developers of Jython now work for Sun. We don't, at this point, have any Python support available in NetBeans. But that will change. Python is another dynamic language we're very interested in, trying to leverage what we put in place with the Ruby support in 6.0. That's what we're leveraging for the JavaScript support, and we're going to leverage that for other dynamic languages as well.

Frank Sommers: NetBeans 6.0 already provided excellent Ruby support. Are there any new Ruby features in 6.1?

Brian Leonard: The biggest change, and this quite large, is support for Rails 2.0. If you follow the landscape between [Rails] 1.6 and 2.0, the architecture changed quite a bit. NetBeans has evolved to support that. Some of the dialog boxes you see, for example, were changed to accommodate for what new Rails 2.0 generators are looking for.

We always tout our out-of-the box experience. With NetBeans 6.0, we shipped Rails 1.2.4, with 6.1 we'll be shipping 2.0 out of the box as the default framework.

Frank Sommers: Could you tell us about some of the new Spring-related features?

Gregg Sporar: What we're trying to do, again, is to improve the out-of-the-box experience. Just like we include the Struts libraries, or the JSF libraries, with 6.1 we're including the Spring libraries. When you create a Web application, one thing you can check is that you want to use Spring. We have some basic support there now, such as code completion for Spring artifacts.

Frank Sommers:: Could you share with us how you decide what languages and frameworks to support in NetBeans?

Gregg Sporar: NetBeans already supports a whole host of frameworks. And framework support is not a Java-only thing. Our support for Ruby wouldn't have been any good if we hadn't had any support for Rails. The same sort of thing will happen with other dynamic languages. One of the things down the road is support for Groovy. And the Groovy community is really interested in their version of Rails, Grails. We not interested in doing Groovy support unless we have Grails support as well.

Frank Sommers: Besides the new features we already talked about, what else is new in NetBeans 6.1?

Tim Boudreau: We did a lot of work in 6.1 on improving startup performance. A modular application is one that discovers its parts when it starts. You want to make that process as efficient as possible.

In previous versions of NetBeans, the startup process did a lot more work than was absolutely necessary. One thing we did was to lazily load projects in 6.1. Inside NetBeans, a project is an object that associates a directory with a bucket of stuff. We optimized how that works, and only show the project root node when you first start the IDE. Then there was a some nuts-and-bolts stuff with optimizing XML parsing and manifest parsing, tuning class loading, reducing the amount of IO that happens. In our regression tests we actually make sure that performance gains are kept over time: if startup takes too long, the tests are going to fail.

What do you think of NetBeans 6.1? What languages and frameworks would you like the IDE to support?


Partha Biswas

Posts: 3
Nickname: parthab
Registered: Jul, 2007

Re: Three NetBeans Evangelists Discuss NetBeans 6.1 Beta Posted: Mar 20, 2008 12:24 AM
Reply to this message Reply
I want Scala, Lua, XMF and Rubinius VM Support.

Regards ~
Partha Biswas

Vincent O'Sullivan

Posts: 724
Nickname: vincent
Registered: Nov, 2002

Re: Three NetBeans Evangelists Discuss NetBeans 6.1 Beta Posted: Mar 20, 2008 1:55 AM
Reply to this message Reply
I'm a long time eclipse user and tried out Netbeans for the first time last week. I only spent a couple of hours on it, so I'm hardly an expert, but I feel little inclination to go back and try it again.

My first impression (and first impressions last) is that it just looks so rough and clunky compared with eclipse. Eclipse is the flagship product for SWT based UI and it looks very, very good. I assume that Netbeans is similarly designed to be an example of how good a Swing based desktop app can look. If that's the case then the answer is 'not very'.

The other problem I had was the amount of time I spent waiting for the application to respond to commands. Certainly there are things in eclipse that take many seconds to complete, but simply switching from one editing tab to another isn't one of them. With Netbeans I was consious of having to wait for the application to catch up every time I changed screen.

Functionally it may well excel eclipse, I've no idea, but if the look and feel remains so dated and slow then - speaking for myself - I feel little inclination to explore further.

I code because I enjoy it. My brief experience of Netbeans was that it was a somewhat leaden UI that I was dragging along, rather than one that pushed me further.

Bill Pyne

Posts: 165
Nickname: billpyne
Registered: Jan, 2007

Re: Three NetBeans Evangelists Discuss NetBeans 6.1 Beta Posted: Mar 20, 2008 6:04 AM
Reply to this message Reply
Without question, Scala and any frameworks associated with it.

Flat View: This topic has 3 replies on 1 page
Topic: Roberto Chinnici on Extensibility and Modularity in Java EE 6 Previous Topic   Next Topic Topic: Cedric Beust on Test Extremism and Test-Driven Development

Sponsored Links



Google
  Web Artima.com   

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