Ohloh flags NetBeans incorrectly, as a mostly JavaScript project

What is Ohloh?
Ohloh is a open source software directory. Ohloh recognizes the open source source control repositories and when a open source project is registered with Ohloh it crawls the source repository directly and generates reports about the activity and nature of the projects.


NetBeans information on Ohloh
When I checked about NetBeans project on Ohloh to add it to my stack of projects I was surprised to read Ohloh mentioning NetBeans as a mostly written in JavaScript project.

Click here to visit NetBeans page on Ohloh

The mostly written in information, as given by Ohloh site, is extracted from the analysis of NetBeans source repository. This means the source of NetBeans mostly contains JavaScript files.


What is the language used to develop NetBeans?
I know that NetBeans IDE is written in Java language. The NetBeans site do not mention this fact any where as it may be taken as a implicit fact. The NetBeans site mentions about the features of NetBeans and what it can do for you but what it is written in is kept implicit, or at least I could not find any page mentioning the programming language of NetBeans IDE. Now as I am subscribed to NetBeans developers mailing list I know from the discussions going on there that NetBeans is developed in Java.

I have added a comment to the Ohloh mostly written by page to highlight that NetBeans is a Java project and not JavaScript. You can also comment on it to add to it.

with regards
Tushar

10 Things NetBeans must do to survive

(NetBeans.org web site in initial days around 2001, obtained from WayBack Machine)

I stumbled upon an old post by Matt Stephens with the title 10 Things NetBeans must do to survive. Matt has reviewed NetBeans version 3.0 probably and the post is dated October 27, 2003. I got tempted to check whether his points hold good today for the current version after around 4 and half years of that review.

1. Improve the windowing system
In his first point he points out towards the windowing system. I have used IntelliJ IDEA and I daily use Eclipse in my day job. I can say the windowing system in NetBeans is according to current standards. Same dockable windows, floating windows and expandable editor windows. I am able to use the windowing system without much difference noticed.

2. Improve Usability
In his second point he mentions options panel, properties panel, GUI panel and Wizards being unfriendly. I have not used the NetBeans version 3.0 so cannot say about these windows in that version. For NetBeans IDE 6.1 I can see the options window, properties window, GUI panel and Wizards according to the current industry standards. If you do not have to learn a feature because it follows already established industry standard then that feature can be called as usable. In fact the GUI builder now have choices to create Java code which is not dependent on any NetBeans library.

3. Improve the default Look and Feel
In his third point Matt mentions default look and feel which in his view was not good at those times. Now I can see my NetBeans IDE opening with the Windows XP look and feel for me. This means the IDE now has smart look and feel features. I even tried changing my look and feel by changing the look and feel entry in netbeans.ini configuration and I now know I can have any look and feel to my NetBeans IDE.

4. Keep enhancing Java Editor
In his fourth point he suggests NetBeans to keep the Java editor up to date. I can see many good features now available for Java Editor. There are some hints missing but I see the Java Editor making progress in each version.

5. Slow down on APIs
Matt expresses unhappiness for the rapidly changing API of NetBeans platform. I can see many books in the market now with the established set of APIs. I feel the API of NetBeans is quite matured now and this point does not hold good now.

6. Make the APIs simpler
In this point it is mentioned that API is not suitable for standalone applications to get developed on the NetBeans platform. I cannot say much for this point. You the reader may have better points and if you do please tell me in comments of the post. What I can say is I have seen some applications developed on top of the NetBeans platform and hence do not feel the APIs are not good enough or simple.

7. Lose the NetBeans is slow stigma
The performance of NetBeans has been improved by the NetBeans team from version to version. The startup time is now fast and many benchmarking reviews are available.

8. Offer built-in refactoring support
Now NetBeans has a refactoring menu for Java refactoring. I can see major refactoring options available out of the box.

9. Make more noise
For this point Tim Boudreau also have stated in comments that hyped publicity do not last long. I can see many users of NetBeans writing about it and this is the most original and first hand publicity a software tool can get. So this point has being covered by different and better means creative of publicity and promotion.

10. Stop using that… brown colour scheme on their website
Here Matt says brown color should be left behind and NetBeans should embrace more professional color. I do not agree much to his point but now NetBeans.org site has different colors that those days. The colors now are blue shades and smooth colors to eyes.

Concluding my review of the review I will say that all the points mentioned by Matt are covered by the new NetBeans IDE 6.1 and not only that the IDE now contains many more improvements and support for multiple languages as well.

If Matt writes about the current version of NetBeans IDE 6.1 again I believe he will agree to all my points and will also add some more praise to the points more than me.

Do read that review also as it contains many comments from many important people with interesting viewpoints. Do comment on my post with your opinion.

Recently I saw some back links for my blog. Many thanks to Ramesh and Jay for the link backs.

with regards
Tushar Joshi, Nagpur