131–140 of 277 posts
Wait, I thought Oracle (Java's current owner) is Apple's friend, because of the lawsuit against Google's Android. Head spinning.
Sounds significant, but how important is Apple/MacOS to Java?
It's unclear whether this is positive or a negative announcement. If another party steps up to maintain a JDK/JRE port on OS X, this will probably end up being a good thing, as Java updates from Apple had been infrequent.
So then what's the best way to do cross-platform development? For all its faults, Java does deliver something that resembles the "write once, run anywhere" dream. Any idea for a high-performance, cross-platform, native UI development stack? Is C++/Objective-C still the best option?
Depending on what you want to do, Adobe AIR would be a practical way of delivering applications on Mac, Win and Linux...
Earlier quoted context omitted.
many SWT apps, using native look and feel, still feel slowish (think azureus/vuze if not eclipse). Some AWT apps are perfectly snappy e.g. jedit opens a file faster than macvim on my box. My belief is that apart form some overhead in AWT against native toolkit, 90% of the laggish experience in java apps is due to poor coding. In turn, this is probably a byproduct of the java platform/language (abuse threads cause the…
do not pay attention to proper data structures cause you can get away with builtin collections etc Specific examples from your experience?
First one I think of (cause I redid it today, in ruby :) is:
you need to keep a list of lines you already processed in a large log analysis. I'd just use a Set (which is a hash underneath) and get done, although I'd have saved a bunch of overhead (memory allocations, gc pressure) using a bloom filter.
I wonder if putting the boot into the most straightforward cross-platform solution for desktop apps has anything to do with the proliferation of OSX Java apps with shoddy/un-maclike UX/UI or whether it's something to do with Oracle's recent moves.
Earlier quoted context omitted.
However it isn't just the Cocoa bindings that are important. AFAIK SoyLatte's Swing/AWT elements run through X11. Apple's Java allows for Java GUIs without starting X11.
Indeed, this will presumably affect users of Eclipse, Netbeans and similar. Not sure how many non-developer apps make use of those APIs, though, especially as they don't quite produce native look & feel. (still much better than X11, which is indeed terrible on OSX)
Earlier quoted context omitted.
X11 is horrible on OSX. Applications that use it (e.g. The GIMP on OSX), are terrible and have many usability flaws, such as no clipboard between an X11 application and a normal application.
True, but would you rather not have it at all?
Earlier quoted context omitted.
> Their move from GCC to clang is no coincidence. Erm... what? Clang has already been ported to Windows (and other platforms). Their move from GCC to clang comes from GCC sucking goat's balls at error reporting and being integrated into an IDE. You might want to note Apple produces an IDE so that's kind-of a big deal for them, and a big reason for the existence of LLVM and related technologies (Clang, LLDB, ...) is v…
Clang/LLVM is BSD while GCC is GPL. That means Apple can extend them all they want without ever giving you, or their competition, any sources. If they ever perceive a threat from their competition, Clang/LLVM provides a lot more maneuvering space than GCC ever would. And yes, GCC is a very hard thing to integrate into tools and it's that way by design.