Posted by editor
on May 4, 2011 at 6:04 PM PDT
The results of a recent java.net poll suggest that, while developers are fairly reluctant to change their primary IDE or code editor, across a long enough time span, most developers do make a change...
The results of a recent java.net poll suggest that, while developers are fairly reluctant to change their primary IDE or code editor, across a long enough time span, most developers do make a change (or multiple changes). A total of 48 votes were cast in the poll. The exact question and results were:
How many times in the past decade have you switched your primary IDE / code editor?
- 27% (13 votes) - Never
- 44% (21 votes) - Once
- 17% (8 votes) - Two or three times
- 13% (6 votes) - Four or more times
- 0% (0 votes) - I don't know
This is of course not a scientific survey, but the results seem reasonable. Switching IDEs takes time and effort, and reduces productivity at least for a while. And, who can afford even a temporary reduction in productivity? So, a switch has an up-front cost that must be balanced by an expectation of future productivity gains that ultimately more than offset the near-term loss.
Still, over the course of a decade, almost three fourths of developers indicated they made at least one switch. This makes sense, because over 10 years, different IDEs/editors will advance at different paces, perhaps new IDEs/editors are introduced that offer attractive capabilities, etc.
The clear bulge in the data is "once" -- 44% of the voters made a single primary IDE/editor switch in the past decade. Meanwhile, 27% stayed with the same primary IDE/editor throughout that period; and 30% switched their primary IDE/editor multiple times.
I'm glad no one said they didn't know how many times they switched their primary IDE/editor!
Our current java.net poll asks "What's your view of Oracle's handling of JavaOne?" Voting will close on Monday.
Since my last blog post (Happy First Year Anniversary, Brussels Java User Group! ), there have been several interesting java.net blogs composed by others:
Our latest java.net article is Deepak Vohra's Using Spring’s AOP Features with Java EE .
Our latest java.net
href="http://www.java.net/archive/spotlight">Spotlight is Java Champion Kirk Pepperdine's Benchmarks Gone Wild Part II, A Hoisting We Will Go :
It’s long been taught that we should avoid performing repeated calculations in a loop. In this installment of Benchmark’s Gone Wild, I’ll examine this performance tip to see the impact it has on the performance of a simple calculation. The first thing we need is some code to benchmark. I’ve chosen the following methods...
We're also featuring Deepak Vohrah's new java.net article, Using Spring’s AOP Features with Java EE :
The popular Spring framework complements and facilitates development on the Java EE platform by providing a modular, object-based programming model. Whereas Java EE is OOP (object-oriented programming) based, Spring is AOP (aspect-oriented programming) based; in fact the AOP framework is one of the main components of Spring. AOP complements OOP...
Here are the stories we've recently featured in our Java news section:
Subscriptions and Archives: You can subscribe to this blog using the java.net Editor's Blog Feed . You can also subscribe to the Java Today RSS feed and the java.net blogs feed . You can find historical archives of what has appeared the front page of java.net in the java.net home page archive .
-- Kevin Farnham