[news.eclipse.tools] Re: Call for screenshots

["Renaud Waldura" <renaud+eclipse@xxxxxxxxxxx>]

> it didn't even have a "File, Open" option on its menus. EVERYTHING
> has to be in some kind of project, and you couldn't even pick
> or choose files in a directory, it would import EVERY file
> in a directory."
>
> Lots of people can't get past Eclipse's inflexible use of the file system.

Allow me to re-phrase that. Lots of people have a hard time with a tool that
implements better practices than theirs. They're attached to their ways
(which they can hardly be blamed for) and it prompts them to turn down, and
complain about, the opportunity to improve.

Going through the bug-tracking system I've found many change requests that,
if they were to all get implemented, would turn Eclipse into a "traditional"
text-based IDE. People complain about the lack of File/Open, the lack of a
Compile button, the incremental compilation, etc. Basically almost
everything that makes Eclipse Eclipse, because it's different than what
they're used to.

Let's face it: Eclipse (the JDT) implements a specific programming
"style" -- inherited from Smalltalk -- that feels new and alien to most
people coming from a static language background. It takes an open mind to
recognize that the programming style made possible by Eclipse is more
productive. Those that don't see this complain about how the tool doesn't
let them propagate their outdated habits.

The current Eclipse release certainely has room for improvement, but I hope
OTI will not dilute the broth just to please a crowd who doesn't "get it".

--Renaud