At first it was stupidly amusing, now it's just stupid.This updated to a source code base that support powerpc64. This is the mailing list for people discussing the development of significant Java applications for FreeBSD and the porting and maintenance of JDKs.It's getting really old. FreeBSD-specific Python issues. Technical discussion of FreeBSD on HP ProLiant server platforms. And not anything specific about it, not even the stupid parroting that it's "slow", just things like "it's an abomination" etc.Porting FreeBSD to the PowerPC® freebsd-proliant.
The fact that Slashdot has now become a playground for groundlessly insulting "Java" in the hopes of scoring a few mod points from the (as usual) hopelessly juvenile Slashdot moderators, makes me sad.I know it's not trendy to bust into your acerbic sarcasm-filled world with my serious comment here. It does offer a lot to users of all platforms, and has been doing so for quite some time now. In fact, it doesn't just suggest this to me. This suggests to me that it offers a lot to users of all platforms, especially open-source ones. Created attachment 204682 details Changes for openjdk11/Makefile I'd propose the following change to openjdk11/Makefile instead.Java is a powerful, performant (by far moreso than the current batch of oh-so-trendy interpreted languages), cross-platform, *open-source* set of technologies.
Leave Java alone.What reaaly bothers me about Apple is that their support for anything that doesn't come out of Cupertino seems to be either designed to bait end users into moving to Macs than anything else.When Apple brought out OS X in 2001, it was all smiles as the system came with free developer tools, a Java-Cocoa API that allowed you to use Java to write native Cocoa apps as well as a C/C++ API that also allowed you to write native Mac apps.The problem was that the Java-Cocoa api was buggy from the start, apart from having very slow response on a, at the time, very slow user interface. As someone who supports and uses Java, I'm getting sick and tired of standing by while Slashdot scheisters such as Mr Coward here hi-five each other every day for upping the Java-deprecation ante.Go poke fun at BASIC or something. There is a wide diversity of tools and technologies out there, all with unique advantages. Yet unfortunately, all you are doing by making these sorts of jokes is needlessly acting to divide a healthy open-source community and reduce enthusiasm for Java. NET missionaries) who would seriously want to see the downfall of Java anytime soon.
Java6 was available for other platforms over two years ago, and now Java7 is even almost here.Seriously, if you're a Java developer, is there any actual reason to use Mac OSX? You're far better off using Eclipse on Linux.Long term, Apple is probably doing what is going to be best for Apple.I have been really heavy into Java development from the start. This is also Microsoft suffers from, in its Embrace and Extend strategy.This had serious repurcussions for Apple in the 90s and I, as a long time Mac user worry if it won't happen again. Apple was known for this in the 90s and there was an acronym for that: NIH -Not Invented Here.
But Adobe also had a really long time to work on a Cocoa port. It's true that Adobe got rather screwed in particular in that at a crucial point in time they were told Carbon was going to last a few more years than Apple is saying it will now. There just is not widespread adoption to date, thus the greatly diminished focus on keeping the Java->Cocoa bridge healthy.As for the Carbon (what you incorrectly label C/C++ API's), well Apple said all along that the plan was to transition to Cocoa, and that Carbon was a bridge to that end.
I think in some ways all companies took the best paths open to them, it just happens here near the end game we have something of a discontinuity.Microsoft I feel less sorry for than Adobe as they have a more purely OS X focused product and don't have to try to engineer a cross platform codebase (as far as I know there's really no Office UI code shared from Windows to the Mac version and the Mac BU is pretty independent).The date was pushed out because Adobe, Macromedia and Microsoft were refusing to move, firstly to Carbon, and later to Cocoa. Adobe/Macromedia and Microsoft had a very long run-at least 8 years more than they were expected with Carbon.But then wasn't the date pushed out as "large companies" had some trouble with transition? I agree that they should have planned to that date but at that point, the date may have been ambitious given the changes OS X and Cocoa itself would undergo in the intervening years. 2007 End of Life for Carbon listed. That was unfortunate for both Apple and Adobe, but in the long run it's going to make everyone switch to a single API sooner which means more support can go into maintaining and improving one API rather than two.As a side note, just because Cocoa is more of an Objective-C API doesn't mean you can't easily call it from C/C++ code.1997 WWDC Carbon transition API released.
Java For Powerpc Bsd Full Version Behind Linux
But what competitive advantage they deem to have when their releases are a full version behind Linux, Solaris and Windows is debatable.Would Apple publish changes back to openjdk? They seem reluctant to. They have sought to maintain their own Java port for competitive reasons such as low level OS integration. Would Sun be willing to 'buy back' Apple's source tree and GPL it? Some OS X internals Apple may not wish to expose (IP issues) and like Sun's codebase be encumbered by code they don't own.Ultimately some of the ball is in Apple's court.
According to the Update , it'll only run on 64-bit Intel Macs with OSX 10.5.2 installed. "Doesn't run on Mac, must run everywhere" is a very solid argument against moving to Java 6.As it happens, I must be new here, and I accidentally read the article.Sadly, a Java 6 app still doesn't run everywhere. Do Apple and Redhat really compete for the same markets, aside from a few Xserves?I was about to say that this matters to the Java Fanbois, in the hope that they would finally get to play with the Java 6 features now that they're supported on the major platforms. Who else have a vested interest in openjdk? Redhat, who have signalled intentions to support multiple architectures besides x86.
This will only affect the tinkerers that happen to be running the latest version of OSX on 64-bit hardware, or developers that are fortunate enough to be able to target an audience that uses modernish technology.So, nothing to see here unless you're a bleeding-edge Java+Mac fanboi.
0 kommentar(er)
