| Update Manager [message #158304] |
Sat, 24 June 2006 00:51  |
Eclipse User |
|
|
|
I'm not sure where to post this so I'll try here...
What's Wrong with Eclipse?
In a word -- UPDATE MANAGER. This has to be the most ill-conceived
program I have ever seen. The absolute worst use of an automatic update
feature I have ever seen takes less than 1 minute to check for updates.
Eclipse can take more than an hour (at dial-up speeds). What is going on?
Here is my top 10 list of absolute horrors in update manager:
[1] IT'S TOO SLOW. IT'S TOO SLOW. IT'S TOO SLOW. IT'S TOO SLOW.
[2] You have to run it twice to check for new features and updates to
existing features.
[3] You can't uninstall old features unless Update Manager installed them
in the first place.
[4] When you select features to install you may get a missing dependecy
error. The error is often completely useless. It may use a descriptor
not found in the list of checked features. It may describe a dependency
but doesn't tell you the feature or plug-in that contains the missing jar.
It runs some ridiculous validation process each time you check or uncheck
a selection. It may or may not highlight the features that cannot be
installed (via the red mark on the icon).
[5] The Details button gives no additional information. What's the point?
[6] The percentage indicator goes by % of features checked or downloaded
(I guess). That is a useless indicator. The logical choice is by
estimated time (e.g. % bytes).
[7] You are reprompted for a mirror every time. Why not remember the last
choice?
[8] Some sites remain checked and some don't. Why?
[9] When you manage your configuration and uninstall an old feature the
tree collapses. If the list of features is long you have to reexpand the
list and scroll over and over.
[10] With my current configuration more than 45Mb (uncompressed) are
downloaded just to tell me their are no updates. Are you kidding?
And here are 2 bonus horrors (just for fun):
[11] There are 3 ill-conceived check boxes ("Show only applicable...",
"Show only latest...", and "Filter...").
[12] It's often not obvious what site(s) to add to Update Manager in order
to install a new feature. Sometimes the answer requires much searching or
posting to a news group to find out. If you decide to punt and just
download the feature(s) and manually install them you won't be able to
uninstall them.
I would like to use Eclipse as my primary IDE. It's the only one to have
a wealth of choices beyond Java. However, after adding each new feature
(CDT, php etc.), especially when the developers are releasing lots of
changes, just makes me dislike Update Manager more and more. Is there any
hope this will be corrected?
|
|
|
|
|
| Re: Update Manager [message #158827 is a reply to message #158304] |
Thu, 29 June 2006 08:41  |
| Eclipse User |
|
|
|
Originally posted by: eclipse4.rizzoweb.com
Keep ranting, and yelling like this and report back to us how far that
gets you and how much change it effects.
Seriously, you probably have some valid points and suggestions for
improvement, but honestly they are drowned out by the tone. And as
someone else pointed out, Bugzilla is the mechanism for
requesting/suggesting change to Eclipse.
Just some friendly advice - I don't really have a problem with, or
particular affection for, the Update Manager.
David wrote:
> I'm not sure where to post this so I'll try here...
>
> What's Wrong with Eclipse?
>
> In a word -- UPDATE MANAGER. This has to be the most ill-conceived
> program I have ever seen. The absolute worst use of an automatic update
> feature I have ever seen takes less than 1 minute to check for updates.
> Eclipse can take more than an hour (at dial-up speeds). What is going on?
>
> Here is my top 10 list of absolute horrors in update manager:
>
> [1] IT'S TOO SLOW. IT'S TOO SLOW. IT'S TOO SLOW. IT'S TOO SLOW.
> [2] You have to run it twice to check for new features and updates to
> existing features.
> [3] You can't uninstall old features unless Update Manager installed
> them in the first place.
> [4] When you select features to install you may get a missing dependecy
> error. The error is often completely useless. It may use a descriptor
> not found in the list of checked features. It may describe a dependency
> but doesn't tell you the feature or plug-in that contains the missing
> jar. It runs some ridiculous validation process each time you check or
> uncheck a selection. It may or may not highlight the features that
> cannot be installed (via the red mark on the icon).
> [5] The Details button gives no additional information. What's the point?
> [6] The percentage indicator goes by % of features checked or downloaded
> (I guess). That is a useless indicator. The logical choice is by
> estimated time (e.g. % bytes).
> [7] You are reprompted for a mirror every time. Why not remember the
> last choice?
> [8] Some sites remain checked and some don't. Why?
> [9] When you manage your configuration and uninstall an old feature the
> tree collapses. If the list of features is long you have to reexpand
> the list and scroll over and over.
> [10] With my current configuration more than 45Mb (uncompressed) are
> downloaded just to tell me their are no updates. Are you kidding?
>
> And here are 2 bonus horrors (just for fun):
>
> [11] There are 3 ill-conceived check boxes ("Show only applicable...",
> "Show only latest...", and "Filter...").
> [12] It's often not obvious what site(s) to add to Update Manager in
> order to install a new feature. Sometimes the answer requires much
> searching or posting to a news group to find out. If you decide to punt
> and just download the feature(s) and manually install them you won't be
> able to uninstall them.
>
> I would like to use Eclipse as my primary IDE. It's the only one to
> have a wealth of choices beyond Java. However, after adding each new
> feature (CDT, php etc.), especially when the developers are releasing
> lots of changes, just makes me dislike Update Manager more and more. Is
> there any hope this will be corrected?
>
|
|
|
Powered by
FUDForum. Page generated in 0.14094 seconds
Home