Linked by Thom Holwerda on Thu 28th Jun 2007 18:47 UTC, submitted by Datatec
Bryan Varner, one of the core developers of the stalled port of Java 1.4 port to BeOS R5 has an interesting post on his blog. Recently he met up with Ian Murdock of Sun at a local Java Users Group, and as a result he is now looking to restart the port, this time for Haiku.
Thread beginning with comment 251511
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Re: Mono would be nice too
by anevilyak on Fri 29th Jun 2007 04:25
in reply to "RE: Re: Mono would be nice too"
Member since:2005-09-14
RE[3]: Re: Mono would be nice too
by TQH ! on Fri 29th Jun 2007 08:00
in reply to "RE[2]: Re: Mono would be nice too"
Member since:2006-03-16
For those interested in Java on BeOS:
http://video.google.com/videosearch?q=java+beos
RE[3]: Re: Mono would be nice too
by bryanv on Fri 29th Jun 2007 12:20
in reply to "RE[2]: Re: Mono would be nice too"
Member since:2005-08-26
Networking is actually fairly complete.
I've not done any gap analysis on it, but we were able to run all sorts of net applications on R5 net_server. Surely BONE was in a better state. :-)
AWT is mostly done. Keyboard handling isn't quite up to snuff -- I was working on that when we finally sorta 'let go' last time... almost two years ago now.
Swing itself is written in Java, so it merely depends on the AWT and a few other key parts being properly finished off.
Java2D - the graphics subsystem, is heavily stubbed at this point. I clearly remember what we had to do in order to get things working, and I'm positive it wouldn't take me (or anyone else who might understand what we were doing) very long to start filling out our non-BDirectWindow implementation. The use of BDirectWindow is still something I dream about (and we could acheive) - but I think at this point we'd be better off using some of the private API's in Haiku to avoid as much of the BBitmap IPC as possible.
Anyhow, networking -- no.
The biggest gaps are in AWT subsystems. KeyEvent generation, FocusHandler, and Java2D.
There were also stability problems imposed by the protect_mem issues.
The biggest problem with moving to the OpenJDK: We're two or three major releases behind, and a lot has happened in the HotSpot VM since 1.4.1. Our tree won't merge easily.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
"This is my NeXTstation Turbo Color booting the Mac System 7.1 Operating System using a hardware add-on called 'Daydream'. The Daydream has a Mac ROM and a few custom ICs in it and hooked up to the NeXTs DSP port. Turns your NeXT into a full fledged 68k powered Mac." So cool.
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
"The NetBSD Project is pleased to announce NetBSD 6.1, the first feature update of the NetBSD 6 release branch. It represents a selected subset of fixes deemed important for security or stability reasons, as well as new features and enhancements. Please note that all fixes in the prior security/bugfix updates (NetBSD 6.0.1 and 6.0.2) are also in 6.1."
Linked by Thom Holwerda on 05/18/13 21:06 UTC
"At the end of a week in which Electronic Arts confirmed it wasn't developing a thing for the Wii U, one of the software engineers in EA Sports' Canada studio, in a series of since-deleted tweets, disparaged the console as 'crap' and suggested Nintendo should give up on hardware altogether. 'The Wii U is crap. Less powerful than an Xbox 360. Poor online/store. Weird tablet', tweeted Bob Summerwill, listed as a senior software engineer at EA Canada, in a reply to a tweet posting a link about EA's no-Wii U news. 'Nintendo are walking dead at this point'." The Wii U is turning into the 21st century's Virtual Boy.
Linked by Thom Holwerda on 05/18/13 7:37 UTC
"In NixOS, the entire operating system - the kernel, applications, system packages, configuration files, and so on - is built by the Nix package manager from a description in a purely functional build language. The fact that it's purely functional essentially means that building a new configuration cannot overwrite previous configurations. Most of the other features follow from this." Interesting approach. A Linux distribution, sure, but with some very refreshing ideas about system configuration.
Linked by fran on 05/18/13 1:38 UTC
Appfour added, among other features, C/C++ support to its new version of AIDE. From Android-IDE, "Now you can write parts of your app or your whole app in C/C++ on your device. AIDE supports the Standard Android NDK toolchain (GCC 4.6 + Bionic, STL, ...). No changes are necessary if you want to build an app developed on a PC with Eclipse. C/C++ development is fully integrated: Build errors appear in the error list and files can easily be navigated to with Go to file. The editor supports C/C++ syntax highlighting."
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Ars nails it: "The answer is that Google did announce what amounts to a fairly substantial Android update yesterday. They simply did it without adding to the update fragmentation problems that continue to plague the platform. By focusing on these changes and not the apparently-waiting-in-the-wings update to the core software, Google is showing us one of the ways in which it's trying to fix the update problem."
Linked by MOS6510 on 05/17/13 22:22 UTC
"It is good for programmers to understand what goes on inside a processor. The CPU is at the heart of our career. What goes on inside the CPU? How long does it take for one instruction to run? What does it mean when a new CPU has a 12-stage pipeline, or 18-stage pipeline, or even a 'deep' 31-stage pipeline? Programs generally treat the CPU as a black box. Instructions go into the box in order, instructions come out of the box in order, and some processing magic happens inside. As a programmer, it is useful to learn what happens inside the box. This is especially true if you will be working on tasks like program optimization. If you don't know what is going on inside the CPU, how can you optimize for it? This article is about what goes on inside the x86 processor's deep pipeline."
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
"It was the only moment I heard regret slip into Otellini's voice during the several hours of conversations I had with him. 'The lesson I took away from that was, while we like to speak with data around here, so many times in my career I've ended up making decisions with my gut, and I should have followed my gut,' he said. 'My gut told me to say yes.'" The world would've been a much different place - Apple would have been less dependant on Samsung for its chips, which probably would've meant less money for Samsung to develop its Galaxy business.
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Glass is getting some love at Google I/O as well. New applications have been released - Facebook, Twitter, Evernote, Elle, Tumblr, and CNN. Perhaps more interesting: the newly announced Google Glass Developer Kit will allow offline applications and direct hardware access - great for hacking and expanding Glass' potential. This kit will really allow hackers to put Glass through its paces.
Linked by Thom Holwerda on 05/16/13 17:04 UTC
"But Beck and Merrill decided that simply banning toxic players wasn't an acceptable solution for their game. Riot Games began experimenting with more constructive modes of player management through a formal player behavior initiative that actually conducts controlled experiments on its player base to see what helps reduce bad behavior. The results of that initiative have been shared at a lecture at the Massachusetts Institute of Technology and on panels at the Penny Arcade Expo East and the Game Developers Conference." Absolutely fascinating stuff. I'm a League of Legends player, and to be honest, the community isn't nearly as bad as some make it out to be. I'm happy Riot games has the guts to employ science to address the issue.More News »
Sponsored Links
Member since:
2005-08-26
Yeah, it's a bear alright.
Much of the class library code for 1.4.1 will be reusable on a current port though, so the platform abstraction is farily well along. It's not done, it's not quite -near- done, but I've been able to run some pretty heavy JDK 1.4 apps on BeOS R5.