Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ide-dev] Java IDEs comparison

I spoke with guys from a web company using Eclipse, @Code, and WebStorm. 
They use Eclipse for the integration with Java Backend and Ant, but they prefer @Code and Webstorm for the speed, and say @code is great for its intellisense
BTW, they don't know all the features of Eclipse 
(I will report details to WTP team)

 - To improve Eclipse editor speed and suggestion accuracy, we'd benefit having architectural descriptions of the underlying eclipse system, and guidelines on how to fix.
If it is easier to understand, it is easier to fix/improve
 - To have more users adopting Eclipse, we should explain in a simple way which are the top features we provide. 
 - To understand how users are currently using Eclipse IDE, we could run a survey, or collect data in Eclipse (perhaps by re-using the AERI structure?)

People who care about IDE consistency would better contribute bugs and patches to Platform UI rather than spend time "just" discussing on whatever council IMHO.

Personally, I could fix consistency bugs easier If you give me a page (a single point of access) with Architectural guidelines, and from there, you point me to related best practices. 
(i.e.) we should fix DependencyInjection in components A, B and C. -> look at these pages explaining the best practices to fix D.I.. 

I think The Architecture Council should periodically check and address most important issues. 

Best Regards,
Patrik Suzzi
Engineer, Eclipse
Platform UI Committer

On Thu, Sep 8, 2016 at 9:51 AM, Mickael Istria <mistria@xxxxxxxxxx> wrote:
On 09/07/2016 07:03 PM, Patrik Suzzi wrote:
I think the Generic Editor and Language servers are an excellent opportunity to grow in the direction of providing better IDEs. Let's invest on this!
Let's not put too much hope in it.
Established editors such as JDT, CDT or Webtools ones are very likely to not adopt generic editor because of legacy and very advanced features available in them. I hope the generic editor will be widely adopted and bring consistency for the future editors, but I don't think it's going to magically solve mistakes that were done in the past and that the most important projects have built on. (not blaming anyone, it's easy to say 'mistake' with 10 years of experience later, but very difficult to anticipate all of them before anything exists)

Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

ide-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top