>>>>> "Konstantin" == Konstantin Ryabitsev <icon@xxxxxxxxxxxxxxxxx> writes: Konstantin> I'll add a little more flamage to the conversation and Konstantin> state that native eclipse is actually not that useful. It Konstantin> doesn't seem to run any faster than JDK eclipse, even Konstantin> though you'd think it would There is a common misconception that "AOT compilation == Super Duper Fast". That isn't true. Performance is tricky and the current crop of proprietary JITs are excellent compilers. I'd expect that you could see the benefit if you ran two eclipse instances on the same machine though (eg try developing a plugin and running a second eclipse to test it), due to the use of shared libraries. Konstantin> a) can't easily install any of the third-package plugins Konstantin> that aren't already packaged into RPMs ATM there is a gcj bug affecting the update manager. This is fixed in gcc 4.1. That said, the RPM-ification of Eclipse doesn't otherwise affect the update manager. You just need to make a new update site in your home directory or the like. I didn't read all of this thread, but going by the Subject... segregating by implementation language doesn't make sense. Instead segregate by functionality. Tom -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
