[followup to .foundation]
-
Please take 15 min. to read this carefully. This will save you most
possibly many time.
-
What is eclipse NOT.
eclipse is _not_ a no-cost production environment
- you have to get commercial plugins to make it work
- for Webdevelopement
- for Model Driven development
- for efficient crossplatform GUI design
- [...]
eclipse is not complete & mature WYSIWYG environment
- Visual GUI editors (VE project) are not mature
- Visual GUI editors do not work across platforms
- HTML / JSP and orther essential visual editors are not provided
- the UML2 project refers to the UML _model_
- a visual UML designer is not provided
eclipse is not a real cross-platform solution
- Windows NT and others are _not_ officially validated
- think twice if you want to validate such huge code-base yourself
- Several eclipse projects do not support e.g. Apple Mac.
eclipse is not a "write once run everywhere" solution
- the promise is not kept within eclipse
- you have possibly to create platform specific GUI code
- you have to provide different installations per platform
*RCP*
- inherits all described cross platform problems
*SWT*
eclipse is not an overall elegant and efficient design
- SWT (platform specific GUI) does not provide an efficient
abstraction layer
- you need to code platform dependent
- no framework is provided to encapsulate this task fully
- several projects suffer already from this (MAC incompatibility)
- SWT is organized as a component
- should be at minimum a subproject
*COMPATIBILITY*
eclipse JDT (Java Development Tools) are not fully compatible
- Eclipse own compiler is not fully compatible to official specs
- Feeback on compatibility issues is not treated in a special way
eclipse is not Java 5.0 capable
- many constructs of latest java release (1.5/5.0) were unsupported
- implementation will delay till 2nd or 3rd quarter of 2005
- although requested by community, adequate early support was not
provided
- depending users and even eclipse.projects suffer now from this
*GOVERNANCE*
eclipse is _not_ honest to new users
- Limitations are not stated clearly on the website
- Many time can be lost, until limitations are uncovered
eclipse foundation's board has _no_ user representatives.
eclipse governance is not transparent
- Board meetings and contents are not announced
- Board meeting _abridged_ minutes are published one month later.
- Staffing decisions (e.g. Webmasters) are kept behind the scenes.
- no further information given
- EMO (Eclipse Management Organization) is _invisible_ in its operation.
- critical feedback is many times ignored.
eclipse developement infrastructure is not really open
- no process defined for influence of voting on Issues
- many Issues are simply ignored.
- several procedures happen effectively 'undercover'
eclipse does not follow their governance and developement processes
- not all described processes are followed in practice
- no issue tracking category available to channelize complaints.
*WEBTEAM*
- the organizational unit "webteam" does not exist
- no issue tracking category available to channelize complaints.
- request to create category were simply _ignored_ by webmaster &
direction
*CONTROL*
eclipse has no decentralized control.
- The Platform Project has very much control.
- depending projects have no strictly defined process to influence
platform
- JDT subproject keeps many highly important subsystems.
- e.g. Compliler (which is at minimum a subproject)
- SWT subproject keeps many highly important subsystems.
- should be at minimum a subproject
*EFFICIENCY*
eclipse foundation is not fast and efficient
- User feedback is not processed immediately
- Even _critical_ issues (like privacy policy) are not processed
immediately
- most essential tasks (like newsgroup monitoring) are not ensured.
- simplest things, like an "office@xxxxxxxxxxx" email are missing.
[...] (some more things)
*FINALE*
- I would not be able to work with a tool where the infrastructure is
in effect not working.
- I've suggested to assist the eclipse foundation practically as an
independent, with the goal of a >=5% efficiency increase within 3
months from now.
- No answer.
-
- I close the eclipse case now quickly, as I cannot deal anymore with
such irrationality and inefficiency (apology! my aggression level has
raised due to several unanswered issues, including privacy policy
complaints)
- Moving on to NetBeans.org now, picking it, starting to work.
The feedback/influence/contribution/information channels look much more
efficient @netbeans.org!
As a conclusion, the product should have a much higher quality.
-
If there is enouth interest, I will possibly write a more detailed
report about eclipse.
Please contact me via email.
Thank you!
-
-
-
Some History / Details:
After an initial compact review of netbeans/eclipse, I selected
eclipse for a deeper evaluation (based on a 'better feeling' that I had).
The things that give me an positive impression are finally the things
that make eclipse fail (SWT, Openness, Transparency, Independency, ...).
Many times expectations were raised based on marketing stuff, or simply
due to the need to find finally the so long awaited solution.
Of course a product cannot always fulfill this expectations in practice.
Same thing for Open Source Projects.
-
You will possibly read some replies on this message, which will state
rationales and justifications against my findings.
I can provide for nearly every statement one or more links within
eclipse.org.
But I am tired. I apologize for not making a detailed report.
The newsarchive of eclipse.org has a bad quality, but here are the
links to my messages:
http://eclipse.org/search/search.cgi?q=ilias%40lazaridis.com&ul=%2Fnewslists%2F&ps=20&m=all
-
I continue monitoring of eclipse.foundation for a while.
cu!
.