The latest java.net poll suggests that NetBeans users are moving quickly to the new NetBeans IDE 6.8 release. This poll was interrupted by the recent java.net outage, so the earliest votes were not counted (unless the people revisited the poll after the outage and voted again). A total of 318 votes were cast after the poll was reopened. The final pattern of voting was close to the pattern before the outage (with the exception noted below), so I think the truncated results are fairly representative of all the voting that occured.
Here's the exact question and the final results:
Do you plan to upgrade to NetBeans IDE 6.8?
49% (156 votes) - I already have
11% (35 votes) - Yes, soon
7% (22 votes) - Probably, once I know it's stable
2% (5 votes) - I'll stick with my current NetBeans version
31% (99 votes) - No, I use another IDE
~0% (1 vote) - I don't know; other
The main difference between the voting before the outage (as I remember it) and the final post-outage tally, is that more people selected the "I already have" upgraded to NetBeans IDE 6.8 option, and fewer selected "Yes, soon," in the post-outage voting. In other words, a swath of people who were going to upgrade to 6.8 soon actually did the upgrade by the time the poll resumed.
Looking just at the NetBeans users who participated in the poll (69% of the total vote), 87% of NetBeans users have already upgraded to 6.8 or will do so soon; another 10% of NetBeans users will probably move to 6.8 once the quirks and kinks (if any) are patched; and 3% will stick with their current NetBeans version. This latter group might include people who consider later versions of NetBeans overly bloated (though recent versions have actually become more modular, even as new features have been added); this group probably also includes people who are satisfied with the NetBeans version they have, don't really need the features in newer NetBeans editions, and/or don't have the time or desire to interrupt their work to learn and adapt to a newer version.
Then, there was that single voter who selected "I don't know; other". That person might be waiting until after the holidays to make up their mind.
Speaking of holidays, it's Christmas where I live (U.S.). But, I wasn't about to let a local holiday stop me from delivering an updated java.net front page and a new Editor's blog, for the many members of the java.net community for whom today is not a holiday! I also didn't want to leave people hanging without the opportunity to participate in a new java.net poll. And so...
That was the Year that was as we know it at this point in time. Here is a look back at some of the popular - well, much visited - threads of discussion on this site in 2009...
I'm conducting a survey about how open source projects are organized. It's part of the www.openeo.biz community initiative which goal is to research organizational structures of open source projects and business models of companies related to them... The survey takes about 15 min and is available at: http://www.openeo.biz/limesurvey/index.php?sid=94442. If anyone would like to share a more detailed description about a project it can be added directly to our knowledge base: http://www.openeo.biz/summary/ or can just be mailed...
If you would like to get any news about Oracle acquisition of Sun, this is not the place you need. I would like to tell you about an interesting coincidence in progressive power. Yesterday my friend gave me a gift: Oracle Sun's Deep Inside (2005)...
Shing Wai's post explains the @ServletSecurity annotation that has been introduced newly in JavaEE 6 (Servlet 3.0 specification). The @ServletSecurity annotation provides an alternative mechanism for defining access control constraints equivalent to those that could otherwise have been expressed declaratively via security-constraint elements in the portable deployment descriptor. There is also a Programmatic approach for adding security (via ServletRegistration.Dynamic API) that has been introduced newly in JavaEE 6, i will talk about it in another post...
GlassFish v3 is out now. This release brings in expanded and mature suport for dynamic languages based frameworks, such as Ruby on Rails, Django, Grails and Lift. Here is a quick update...
In the Forums, mixaz wonders about Using floats in LWUIT: "I think it would be better to not use CLDC 1.1 float in plain calculations like scrollbars (and not use at all - it's a UI library, not a math app after all). That's odd... Standard approach is to use 2 integers instead, isn't it? ..."
nnjones has questions about Optimizing the environment to fit with the rendering algorithm: "Can anyone give an overview of the client rendering algorithm in the context of optimizing the world layout to minimize time to load? For example, if the starting location can't see much more than grass, then will the avatar drop more quickly? ..."
Registered users can submit event listings for the java.net Events Page using our events submission form. All submissions go through an editorial review before being posted to the site.
Archives and Subscriptions: This blog is delivered weekdays as the Java Today RSS feed. Also, once this page is no longer featured as the front page of java.net it will be archived along with other past issues in the java.net Archive.
Previous Topic
