“Eclipse Photon likely to focus on usability and performance”
Eclipse Oxygen is here but even though this milestone has been successfully reached, the development continues — next in line is Eclipse Photon. We talked to Lars Vogel, founder and CEO at vogella about his favorite Eclipse Oxygen features, its successor Eclipse Photon and the future of the classic development environments.
JAXenter: Eclipse Oxygen has just been released. Which features of your project(s) did you look forward to the most?
Lars Vogel: Personally, I am enjoying the new option of running all the processes in the background by default. This means there aren’t as many annoying pop-ups asking you if you want to run the blocking dialogue in the background. I also like the fact that most of the platform and git dialogues now have descriptive verbs such as save or don’t save instead of ok and cancel. This makes using the Eclipse IDE much more comfortable. These changes are just small improvements, but they are very helpful to me and hopefully to all the users out there, too.
JAXenter: Which other project/projects fascinate you this year and why?
Lars Vogel: The Git tooling is being actively developed and the team – especially Thomas Wolf – seems to have a soft spot for usability. As a hardcore Git user, it is nice to see what they are doing. Using Mylyn Wikitext for writing documentations with Asciidoc is now much more comfortable, which is another tool that our team is using frequently. The Gradle tooling is getting more and more mature, which is why I avoid using the Maven tooling for Eclipse as much as possible.
The Language Server Protocol (LSP) that was developed by Microsoft, Red Hat and Codenvy will be one of the hot topics in the time to come.
Eclipse Photon & the future of classic IDEs
JAXenter: The next Simultaneous Release will be named Eclipse Photon. Do you have any plans for your project in Photon yet?
Lars Vogel: The focus will have to remain on improving the usability and the performance of the Eclipse platform.
JAXenter: How does the future of the “classic IDE” look? Will new technologies force the “classic IDEs” to a complete redesign?
Lars Vogel: The Language Server Protocol (LSP) that was developed by Microsoft, Red Hat and Codenvy will be one of the hot topics in the time to come. With it you can easily implement the support for new languages or new language versions into your tooling, like Visual Studio Code, Eclipse and also VIM.
JAXenter: What could be made better in the Eclipse IDE or the Eclipse ecosystem in general?
Lars Vogel: Oh, there is always a lot to do. I hope, for example, that the development of the Java tooling will gain momentum again. I am still waiting for the integration (after another revision) of the existing Postfix code completion patch by the JDT team.
As far as the ecosystem is concerned, we have to continue our work to make accessing the Eclipse project easier and more attractive.
JAXenter: Besides Eclipse, which tools/technologies have the potential to “cause a stir” in the second half of 2017?
Lars Vogel: I am probably a little late with that, but I am totally excited about Spring Boot, which we are using internally now. And I already mentioned the Language Server Protocol and Visual Studio Code.
Thank you very much!