And 32-bit on a 64-bit laptop still does make sense.
32-bit does take less memory and is unto 20% faster.
Regarding old laptops, I crawled Wikipedia a bit:
The last Intel microprocessor without the 64bit architecture seems to be the Pentium 4E (introduced February 2004). The first that did support it (Pentium 4F) was introduced in February 2005. [1]
Which would make them roughly ten years old.
AMDs 32bit processors seem to have come to an end with the low-power Turion (introduced October 2010) [2], but they still sell the ultra-low-cost 32bit Geode (probably not powerful enough to run Eclipse).
Those Turions would be around 5 years old now.
Of course, Lars is correct in pointing out that users would need 64bit JVMs. I can imagine that the RCP package is probably most affected by this, others (like Scout) probably less.
If the consensus is going to be to keep it, I’d suggest that we adjust the download site to recommend the 64bit version (with a notice to get the 64bit JVM).
Regards,
Patrick
[1] https://en.wikipedia.org/wiki/List_of_Intel_microprocessors
[2] https://en.wikipedia.org/wiki/AMD_Turion (bottom of article provides a nice overview table)
From: epp-dev-bounces@xxxxxxxxxxx [mailto:epp-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Mittwoch, 17. Februar 2016 16:22
To: Eclipse Packaging Project
Subject: Re: [epp-dev] Can we drop 32bit EPP Packages?
I also suspect a lot of people are running Eclipse on older laptops that are still running 32-bit. In my opinion, it's not time yet.
BTW, as a note on download numbers. We need to be careful in how we interpret them. The bottom 7 or so packages have suspiciously similar download numbers. I'm pretty sure we have a significant number of bots grabbing copies at regular intervals. I haven't run the breakdown in a while, but we should really get the numbers per package before making a decision based on the data.
Doug.
On Wed, Feb 17, 2016 at 7:27 AM, Lars Vogel <lars.vogel@xxxxxxxxxxx<mailto:lars.vogel@xxxxxxxxxxx>> wrote:
I think it is clear an everyone but just in case: to run a 64 bit
Eclipse you need a 64 bit JVM.
As long as Oracle provides a 32 bit version for the JVM I think we
need to provide also a 32 bit version or Eclipse. Several users I know
of use still a 32 bit JVM.
On Wed, Feb 17, 2016 at 9:57 AM, Markus Knauer
<mknauer@xxxxxxxxxxxxxxxxx<mailto:mknauer@xxxxxxxxxxxxxxxxx>> wrote:
Hi Patrick,
good question... I thought about the same idea some months but even when I
check the download numbers today, there are in my opinion too many downloads
of the 32-bit version. Running a (very simplified) query today which
includes data from the last 12 months just for the Mars release (2015-02-17
to 2016-02-17), I see a total number of about 14 million downloads and only
about 10 million downloads were 64-bit downloads. Subtracting this leaves 4
million downloads for 32-bit packages which is a very high number. For the
time being I would continue to build the 32-bit versions.
The configuration itself is defined in the parent pom in the Tycho target
platform configuration, and is the same for all packages.
Regarding the follow up question: Yes, the 64-bit packages should probably
be the default if no one comes up with good reasons why we shouldn't do so.
Maybe this helps changing the statistics over time towards 64-bit, who
knows.
Regards,
Markus
On 17 February 2016 at 09:37, Patrick Bänziger
<Patrick.Baenziger@xxxxxxxxxxxxxxxx<mailto:Patrick.Baenziger@xxxxxxxxxxxxxxxx>> wrote:
Hello all,
We in the Scout project recently debated whether we should continue
supporting (read: build and test) for 32bit architectures.
As far as we can see, all EPP Packages also have a 32bit version built
(except for Mac OS X) and we did not yet find an option to configure
otherwise.
Our reasoning is that with all the OS and Java versions we do test, the
test matrix is getting very large and hard to cover. And second, of all
customers and other users we know, none of them has a 32bit system.
We do not know if it is required to build or support the 32bit
architectures (the SimRel Requirements [1] are not clear on that) and would
like to ask for your input.
· Is it allowed for a project to only provide 64bit packages?
· Can we configure this?
And maybe a follow-up question:
· Should maybe the 64bit packages be the default on the download
page – and the 32bit only if the user explicitly selects it?
(Ubuntu, for example, shows the architecture in a drop down box with 64bit
being the default, labeled “recommended”)
Regards,
Patrick
epp-dev mailing list
epp-dev@xxxxxxxxxxxepp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev
epp-dev mailing list
epp-dev@xxxxxxxxxxxepp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev
--
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH
Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxxlars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com
epp-dev mailing list
epp-dev@xxxxxxxxxxxepp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev
