Even with "most of" I doubt you're right. Point-by-Point: 1. Even if NetBeans had 100% of the IDE market, not that much changed. As I already wrote in the OP, NetBeans runs just fine on non-apple JVMs on macs. A little bit of spit and polish to deal with the new X11.app based chrome would be a fine plan, but we're talking a man- month or so of effort here, tops. Nothing like the serious effort that would be required to port swing to cocoa (at least, if apple doesn't contribute their work in this for their now deprecated JVMs to a community effort or Oracle) - but as a backup, that option (porting swing to cocoa) is there in addition to running netbeans on X11. You could also port netbeans to SWT, but that's not going to happen.
2. Yes, swing is used far more than SWT. But that isn't the point. The point is: A glass of water might be more than a thimble, but compared to the ocean it's nothing either way. Same here: Nobody writes swing apps with the intent to distribute it to apple consumers. Its either used in-house (where apple has a tiny marketshare and you can probably deal with the X11 chrome and installing a JVM), or only used by geeks who are capable enough of installing a JVM and dealing with the odd chrome. Don't mention azureus/Vuze, as that's SWT. 3. Without proof that the image manipulation libraries are significantly slower on Macs on OpenJDK vs. on Macs on AppleVM, I don't believe you. On Oct 27, 6:34 pm, Fabrizio Giudici <[email protected]> wrote: > On 10/27/2010 11:37 AM, Neil Bartlett wrote:> Hi Moandji, > > > Yes that's true, but I don't think that use case will be affected. > > Those classes are not going to be removed. > > > If you'd like to supply a fragment of test code using AWT image > > manipulation, I can verify that it works. > > My 90% was an hyperbole and I apologize for having used a number instead > of a generic expression. In any case: > > 1. Two polls this year reported at 30-35% the percentage of NetBeans IDE > users > 2. I don't have numbers, but in my perspective Swing users are much more > than SWT. It can be subjective. > 3. AWT image manipulation would work on SoyLatte, but without any image > acceleration or particular optimization. Furthermore, imaging > implementations have very different performance figures in function of > some parameter (e.g. the SampleModel) and the operating system. It's > likely that people will have to re-tune their code. > > At last, yes, JVM has not vanished yesterday, but we know it will be > vanished at a certain point, and almost surely for people who will > upgrade to Lion next summer. For the rest, we're still speculating, but > (JKoala apart) there's no news of anybody moving on to fill the gaps. > > -- > f.g. -- 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.
