Thanks a ton for the extremely informative presentation. Such updates are rare as far as Eclipse is concerned. I hope she'll thrive in the future. The Eclipse eco-system has always been a master piece in the software world ever since her birth. She was originally named Visual Age for Java around the year 2000. However, when it was crafted more than 20 years ago, the computer hardware was slow, limited, and expensive as well as Java's poor performance and terribly high resource consumption, all these factors did much harm to her popularity. The coming of VS Code, Intellij IDEA and her siblings, etc. seem to have been worsening her being neglected. It's interesting that the master mind behind VS Code is Rich Gamma, who was once working behind the Eclipse eco-system and Visual Age for Java. He is one of the Gang of Four, who authored the milestone book in the software world, Design Patterns - Elements of Reusable Object Oriented Software. Remember me to one who lives there. She once was a true love of mine.
We use both 3.x and e4 in our company's product. How I did it was we had 3.6 app for years and then we wanted to use e4 features so we considered migration to e4, but in the end we ended on compatibility layer...meaning we can still use many of the 3.x features and use the e4 features (i say some because i had to reimplement some parts of our app to e4 way for it to work). It's much less effort to keep it at compatibility layer then migrating to pure e4, esp. in bigger projects. But in pure e4, which is also those that you create from scratch in Eclipse as e4, idk if and how you can use 3.x components there. I'm sure I've read somewhere that you can't include 3.x plugins in pure e4 app. Maybe he's meant compatibility layer? EDIT: after watching the video, yeah he is talking about compatibility layer in this case
Thanks a ton for the extremely informative presentation. Such updates are rare as far as Eclipse is concerned. I hope she'll thrive in the future.
The Eclipse eco-system has always been a master piece in the software world ever since her birth. She was originally named Visual Age for Java around the year 2000. However, when it was crafted more than 20 years ago, the computer hardware was slow, limited, and expensive as well as Java's poor performance and terribly high resource consumption, all these factors did much harm to her popularity. The coming of VS Code, Intellij IDEA and her siblings, etc. seem to have been worsening her being neglected.
It's interesting that the master mind behind VS Code is Rich Gamma, who was once working behind the Eclipse eco-system and Visual Age for Java. He is one of the Gang of Four, who authored the milestone book in the software world, Design Patterns - Elements of Reusable Object Oriented Software.
Remember me to one who lives there. She once was a true love of mine.
Why is Eclipse RAP not even mentioned? wouldn't it address most of the future scenarios?
You said If we use new eclipse with any of version starting from 4.x we can use old features. But in my case, I am not able to use...
We use both 3.x and e4 in our company's product. How I did it was we had 3.6 app for years and then we wanted to use e4 features so we considered migration to e4, but in the end we ended on compatibility layer...meaning we can still use many of the 3.x features and use the e4 features (i say some because i had to reimplement some parts of our app to e4 way for it to work). It's much less effort to keep it at compatibility layer then migrating to pure e4, esp. in bigger projects.
But in pure e4, which is also those that you create from scratch in Eclipse as e4, idk if and how you can use 3.x components there. I'm sure I've read somewhere that you can't include 3.x plugins in pure e4 app. Maybe he's meant compatibility layer?
EDIT: after watching the video, yeah he is talking about compatibility layer in this case