[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.tools] Re: the mozillafication of eclipse


discuss the lessons that Eclipse can learn from Mozilla.  The article is
available on my brand-spanking-new weblog, located at:

http://ranganath.com/~anoop/

Here is an excerpt, which is also the thesis:

With all these similarities, Eclipse can definitely learn something from
Mozilla. I believe this should be the first lesson: Over the years,

User friendly and expert-unfriendly has been the death of many tools.
Your analogy doesn't work for me because I see mozilla and eclipse as targeting entirely different audiences (both in terms of size and expertise and activity scope -- creation tools have a substantial larger/more challenging set of problems to solve when compared with pure viewers (Ok.. I know about mozilla's mail/news, web page editing support etc. but the % of users that explore/use them regularly is not very high)).


Now -- my pet peeve of eclipse is that it has not learned from the lessons of emacs. Extensibility is a good goal, but you can do it the wrong way or the right way. Done right, it should be easy to have emacs as my editor within eclipse -- has anyone gone and done that yet?

Should less used functions just fall off.. well XP/Win2K's start menu experimented w/ that, and I must say that the lack of predictability that implies .. makes it extremely annoying.

Perhaps you could say specifically about what you find annoying about Eclipse.