This in a nutshell is the kind of "usability screwup" (as you put it 
Reinier) that led me to use NetBeans instead of Eclipse many years ago.

At the time Eclipse's downloads were much worse than today -- with the 
Java perspective being a separate download, etc.  That and the whole 
messed up "perspective" experience when I tried to actually use the IDE 
drove me to NetBeans (which I downloaded, installed, and became 
sufficiently productive with in the morning and had dedicated the 
afternoon to doing the same with Eclipse -- and couldn't).

Now NetBeans has ticked me off innumerable times since -- it's far from 
perfect, but it has never quite pushed me to Eclipse.  [It has come 
close on some occasions due to its scanning issues, though.  Why can't 
the NB team apply some real focus on making scanning block nothing in 
the GUI and be fully incremental in nature?  I can only assume the 
marketeers and others with an overt lust for new feature bullet items 
are in charge of priorities...]

--
Jess Holle

Reinier Zwitserloot wrote:
> Bill: That is indeed it, but it's being released only by the eclipse
> core team, which is why only the 'classic' bundle offers that
> download.
>
> If you want another bundle, you're out of luck. You have to take the
> classic bundle, and then use the plugin architecture to grab the rest.
>
>
> On Aug 11, 6:46 am, Bill Robertson <[email protected]> wrote:
>   
>> Gentlemen please be nice.
>>
>> At the bottom, I do see a "Mac Cocoa  32bit   64bit" link in the
>> "Eclipse Classic 3.5.0 (161 MB)" section.  Perhaps that's it.
>>
>> On Aug 10, 7:14 pm, Reinier Zwitserloot <[email protected]> wrote:
>>     
>>> I'm not out of date; that's the same eclipse I run.
>>>       
>>> It isn't, however, anywhere on the standard eclipse download pages.
>>>       
>>> It would therefore be a proposterous usability screwup if you demanded
>>> your users to somehow find that download.
>>>       
>>> On Aug 10, 3:45 pm, Neil Bartlett <[email protected]> wrote:
>>>       
>>>> Reinier, you're out of date. Eclipse Galileo supports Cocoa and runs
>>>> on 64 bit Java 6 VMs on Mac OS. I've been running Eclipse under Java 6
>>>> for about 6 months already. So the only "hoop" that Eclipse users have
>>>> to jump through is to download the current release version.
>>>>         
>>>> Regards
>>>> Neil
>>>>         
>>>> On Aug 9, 2:05 pm, Reinier Zwitserloot <[email protected]> wrote:
>>>>         
>>>>> Until /very/ recently, the default JVM used to start java apps on mac
>>>>> os x was 1.5; 1.6 has been on macs for ages, but unless you use a
>>>>> mechanism where you can specify which VM you want (e.g. webstart),
>>>>> you'd get 1.5. Fortunately, at least today, any leopard user that has
>>>>> not got automatic updates turned off (Like 90% of all mac os x
>>>>> deployments out there have leopard with automatic updates on, so
>>>>> that's good) have 1.6 as a default.
>>>>>           
>>>>> There's still the Mac Os X 1.4 tiger folks, the folks with a 32-bit
>>>>> CPU, and the need to run with 32-bit libraries (such as *ALL* eclipse
>>>>> installations - if you're writing an eclipse plugin, do NOT USE 1.6
>>>>> only features, or mac users have to jump through a lot of hoops to use
>>>>> your plugin), but that's more of a niche thing at this point.
>>>>>           
>>>>> So, yes, just since this month, 1.6 is okay.
>>>>>           
>>>>> Having said that, project lombok runs in 1.5 and 1.6, and I even
>>>>> replicated the SPI service loader mechanism which is 1.6 only to avoid
>>>>> a 1.6 dependency, because of that eclipse issue.
>>>>>           
>>>>> On Aug 9, 11:05 am, "Vince O'Sullivan" <[email protected]> wrote:
>>>>>           
>>>>>>> Personally, I'm still supporting Java 5 for a number of libraries
>>>>>>> (BetterBeansBinding, jrawio, Mistral) because Java 5 is not yet EOL for
>>>>>>> a couple of months ;-) but above all because I presume a lot of people
>>>>>>> will keep on using it for several time. At the moment I don't need
>>>>>>> specific Java 6 features for those projects and running "matrix" tests
>>>>>>> with Hudson makes not too hard to maintain this stuff - with the
>>>>>>> exception of a specific problem.
>>>>>>>               
>>>>>>> For my own applications I've moved to Java 6 several months ago.
>>>>>>>               
>>>>>> I'm in much the same position.
>>>>>> 1.6 at home, since it came out.
>>>>>> 1.6 on our departmental UAT server since Friday (2009-08-07) but
>>>>>> without any development targeting it yet (chicken and egg situation).
>>>>>> 1.5 on our departmental live server (and all the other servers in the
>>>>>> company that I'm aware of) for the forseeable future.
>>>>>>             
> >
>
>   


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "The 
Java Posse" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to