This is the first code update in a while... New in this release:
- Moved all code repositories to Git. These can be browsed via GitHub.
- Updated Download module and Links section to reflect new locations for all resources.
- Updated the site to Maven 3. There was some significant bitrot in the codebase that needed to be cleared up to get this working.
Other upcoming changes include:
- Move from deployment as a Tomcat WAR file to a standalone app embedding Jetty. This should result in faster restart times and decreased resource utilization.
- Remove CardSpace support as it has been deprecated by Microsoft for some time now and never really gained wide adoption.
- Update libraries to more current versions. For example, update to Spring 3.2 (using 2.0 currently).
- Move to using HTTPS throughout the entire site.
You may or may not have noticed a redirect on this site to http://randomcoder.org/. This domain has recently become available, and since the focus of this site is very much community-oriented, a .org seemed more appropriate than a .com.
Read on for a summary of the final day of JavaOne 2010.
More tales from JavaOne 2010 - Wednesday sessions...
Read on for summaries of the sessions I attended on Day Two of JavaOne 2010.
JavaOne 2010 is over now, and I intend to post a write-up of each session I attended throughout the week. Read on for my impressions of the opening keynote Sunday and the Monday sessions.
So... I just finished installing the beta of IE 9 in a Windows 7 VM and so far, I'm struck by a few things...
First, it's basically the same UI as early Chrome builds (minimalistic), but in Microsoft BlueTM instead of Google BlueTM. There are some minor differences, like the fact that the tabs go on the same line as the address bar, and confirmation dialogs pop up from the bottom instead of down from the top.
Second, performance, while decent, is nowhere near what I would have expected given the hype this browser has received. I tried out several of the HTML5 demos on the Microsoft IE9 Demo Site in both Chrome 6 and IE9 and neither one could manage more than a paltry 10fps on most of them, and this is on a fairly fast Mac Pro. To be fair, IE9 was probably somewhat hampered by running in a VM, but does Microsoft really expect us to believe that by the time IE9 ships, these demos will be smooth as butter? Seems like they may be a bit ambitious...
Finally, standards compliance. There's still some bugs, but this is so much further ahead than where IE8 (or any previous Microsoft product) was, that I'm fairly certain pigs are going to fly and cats and dogs are going to start having little barking fuzzy offspring... I never would have believed it possible. Too bad that it's still going to take at least a decade until we can be sure that IE6, IE7, and even IE8 will finally be a distant memory, especially since IE9 will not run on XP or Vista.
In short, I welcome Microsoft back to the web, and at the very least, this will someday make us web developers' lives easier. And, it should at least make the web a bit less of an ugly place for users too (especially the IE6 crowd).
I've decided that it's about time I started blogging again, and what better time than JavaOne 2010?
I've fortunate enough to be able to attend this year, courtesy of my employer, and it's shaping up to be an interesting conference. Some interesting questions I hope to get answers to next week:
- Will Oracle sue the entire universe (just like they are doing with Google) over the use (or not) of Java?
- Will Java 7 ever come out?
- If either of #1 or #2 occurs, will the fact that Sun open-sourced Java into OpenJDK save us all?
In all seriousness though, I'm looking forward to hearing what the future of my favorite language/development platform has in store, and I plan to post it all right here, so stay tuned...
Microsoft has recently announced that Internet Explorer 8 will contain not one, not two, but three different rendering modes: Quirks mode (IE6), Standards mode (IE7), and We'll-Try-HarderTM mode (IE8), from here on referred to as WTH.
IE8's WTH mode is basically what other standards-compliant web browsers, like Opera, Safari, Firefox, and pretty much any other browser that's Not-IETM, do already, namely render the pages to the best of their ability and stick to the standards as closely as possible.
Rather than follow suit and make IE8 render things like everyone else does, Microsoft has decided to bring us back to the bad old days of browser sniffing, content negotiation, and general suckiness that was the web before browser makers got serious about supporting real standards. To get IE8 to render in WTF mode, you need to include a Microsoft-specific META tag (or equivalent HTTP header) on every page. To make matters worse, we must be living in some sort of twilight-zone inspired alternate reality, because long-time standards advocate site A List Apart has gone over to the darkside and is actively shilling for Microsoft's asinine stance on this.
Instead of adding my two cents about why this is bad, I'm going to take another approach, and suggest a solution: Don't drink the Kool-Aid. Boycott the X-UA-Compatible header Microsoft is pushing, especially if you are concerned about coding to standards. Why? To force Microsoft to abandon WTH mode, make IE8 standards-compliant by default, and stop this ridiculous cause once and for all.
We can do this. By Microsoft's own admission, they are relying on those of us who care about standards compliance to add this tag to our pages; they don't expect older sites to do anything at all. Instead, just keep doing what you're doing -- writing standards-compliant sites. IE's market share is declining, and by the time IE8 ships and is widely deployed, it will likely be even less. Now is the time for standards to reign, not vendor lock-in. Make your voice heard!
There appears to be some hope for Java developers on the Mac platform... it is now possible, thanks to Landon Fuller, to build Java 1.6.0_03 on Mac OS Leopard.
I can confirm that this works, at least for non-GUI code. I successfully compiled and ran a 64-bit VM. 32-bit was more problematic; all attempts at building caused a JVM crash which I was not able to overcome.
Details and benchmarks after the fold.