The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Scott Delap on Oct 15, 2007
InfoQ talked with Ann Oreshnikova of Jetbrains about the release. Oreshnikova was first asked about how Jetbrains views the Java IDE market and the competition of the products in it:
Java IDE market keeps evolving, and this is the most pleasant thing about it. We all know that evolution is a natural result of competition. With regard to it, the Java market today is indeed very special. Competition here is not even because of slightly different audience segments targeted by different vendors. To tell the truth, we believe that competition between the 2 free tools is much tougher that between any one of them and IntelliJ IDEA. As for the segments where we might compete, our main weapons are: innovation, highest quality, productivity that we ensure and pleasant development on top of that. These are actually the main reasons why the number of our customers is not just enviably stable, but keeps growing.
The topic then shifted language support including Groovy, Ruby, and Flex:
Ruby and Groovy are gaining more and more popularity in the development world. Among IntelliJ IDEA users there are many followers of these new technologies, and their requests for support have played a decisive role in adding Ruby and Groovy to this new version. Getting back to your question about the trend, I would say that yes, IntelliJ IDEA is already a cross-language IDE, and is going to continue being such.
InfoQ then asked Oreshnikova about the fact that IntelliJ IDEA 7 includes a number of "why now" features in 7 such as Hibernate, Spring, and Maven support. All of these projects have been around for several versions of IntelliJ:
At first glance, this is a reasonable question, but on the other hand we have to admit that even being around for several years Spring and Hibernate have become the de facto standard not longer than a year/year-and-a-half ago. So, when it happened, it was a sign for us to include them into our roadmap. One can say that they appeared too late in IntelliJ IDEA, but it’s better to be a bit late and bring the best in the market support.
The conversation then shifted to the most difficult feature to develop:
Hmmm. This is a tough question. Many of them were rather difficult and challenging, just from different aspects. If I had to pick one that was technically especially hard to solve, it would be multi-core/CPU support. We had to really fight with it, but the performance leap that we achieved in the IDE editor is definitely worth all those efforts.
Finally, Oreshnikova was asked about the next evolutionary change coming for IDE's:
It’s true. Development tools not only reflect the existing development trends but also form them. As for the next evolutionary change, we believe that it’s going to be the so-called polyglot programming (I have borrowed this term from Neal Ford as it nicely applies to the modern trends). When widely adopted, the polyglot approach may even affect architectural decisions, not only everyday programming techniques. Thus an IDE capable of supporting productive multi-language development, through seamless language and framework integration, should become the best developers’ friend.
SCM best practices for multiple processes, releases & distributed teams
A Guide to Branching and Merging Patterns
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Hi, Scott! Thank you for sharing this interview with us!
Do you know if some issues with the performace were fixed in general? I have used IDEA and noticed it could hang on time to time. I believe it could be adjusted, and I feel the progress of the IDEA team form the 3rd version till the 6th. It is great progress, but the computers also becomes faster...
Still seeing at the release notes on perfomance I believe they did it better:
IDE startup speed greatly improved
JSP editing speed accelerated
More operations performed in background (Find Usages, VCS update etc.)
Improved performance on multi-core CPUs
Faster XML reformatting
Faster project loading
Improved files synchronization speed
Revamped Local History engine
Thanks.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
1 comment
Watch Thread Reply