Packages are good because they provide a nice starting point for the
user since they aggregate the most common features together (e.g. Java
or Java EE).
I think we could improve the situation by:
- Getting rid of some of the obscure / too narrow focused packages.
- On first start, prompt the user with a customization wizard that let
the user add more plugins to his Eclipse. For example, it could ask
questions about the language being used, the SCM, etc.
- Breaking down the barrier of Foundation built software vs the rest of
the ecosystem so the wizard mentioned previously could show content
available from Eclipse Market Place.
On 07/30/2013 12:35 AM, Konstantin Komissarchik wrote:
There are twelve packages currently listed on the downloads page, not
counting the promoted ones. Are so many packages actually a benefit to
users? We try to define packages based on developer profiles, but real
developers rarely fit a profile. One of the most common complaints
that I have seen on forums are related to difficulties in getting an
Eclipse installation that has all the pieces that the developer
requires. The ironic thing is that we go through a lot of trouble to
define a common repository with components that are known to work with
each other, but then fragment the result into a dozen different packages.
Would user experience be better if there was only one Eclipse package
on the main download site that had pretty much everything that's in
the aggregated repository?
Some of the reasons for not doing that...
1. *The package would be too large.* With modern download speeds, I
suspect most users would rather wait a few minutes longer for Eclipse
to download than spend time later trying to figure out how to install
the missing pieces. The disk space difference is also inconsequential
these days.
2. *The users prefer to not include pieces in their installation that
they don't use.* I can see that being the case for some advanced
Eclipse users, but I don't believe this holds true across the user
base. I suspect that most users would rather spend time on their
development project than tuning their Eclipse installation.
3. *Too many plugins in one installation leads to poor user
experience.* If there are problems like that, we should be identifying
and fixing them.
Thoughts?
- Konstantin
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
