post it here.
post it here.
It's an all Emma all the time type of night. ;)
I probably start up a JVM a thousand times a day. Test runs, benchmark runs, bug confirmation, API exploration, or running actual apps. And in many of these runs, I use various JVM switches to tweak performance or investigate runtime metrics. Here's a short list of my favorite JVM switches (note these are Hotspot/OpenJDK/SunJDK switches, and may or may not work on yours. Apple JVM is basically the same, so these work).
If you write any serious Java at all, I highly recommend that you click the link above and read his post. It is full of many amazing gems that I can see being really useful for optimizing and debugging Java applications.
I think I've completely figured out why while I'd like to buy an HP laptop (given that I work for them), I still haven't quite found one that would work for me. I'll start by breaking down the general laptop categories:
While it seems like they may make a laptop for everyone, there's actually a missing segment in here, and I'm smack dab in the middle of it. At first glance, one might think that this segment is best served by the business laptops, since we tend to be knowledgeable about computers, and want a high amount of value for our money. We are very similar to the people that make the business purchasing decisions and care about many of the same things. The big difference is that we are also consumers, so we do care about aesthetics, which means that while we might buy the business laptop because it's a better value than the premium Voodoo laptop, we really want something that looks as nice as the Voodoo laptop, without the Voodoo premium.
I don't think you'd be surprised at all when I say that Apple seems to get this, and makes laptops that balance the needs of the consumer with those of the computer savvy. Apple doesn't really have a distinction between consumer and business lines; everyone gets the same laptop. (The Pro thing really is more of a performance distinction, nothing more.) While there are plenty of things in the Apple laptops for us geeks to complain about, there's very little in the way of huge issues, and it's amazing how much good support can make up for.
So while I've been contemplating my future computer purchases, and thinking that I might be able to get away from the cult of Mac, it seems that if I want to buy a laptop in the near future, I may not be able to beat the MacBook. Counter arguments are more than welcome. :-)
The Rhodes framework is an open source Ruby-based platform for building locally executing, device-optimized mobile applications. It is similar in concept to MVC frameworks such as Rails, Merb and Camping but much lighter weight (and hence executable on a mobile device) than any of these. Along the way of course, we had to implement Ruby for these device operating systems (iPhone, Windows Mobile, RIM and Symbian).
In general, developer productivity is much higher in Rhodes than writing to diverse native device operating systems and APIs since most of your UI customization can be done in HTML templates (ERB files). Rhodes also provides access to native device capabilities such as GPS and PIM data via an extended set of tags (e.g. <geolocation/>).
These applications are also optimized for interacting with hosted enterprise app (SaaS) backends . That is, it allows mobile applications to work offline with synced local data by embedding a client for RhoSync. The Rhodes source tree contains sample apps for SugarCRM, Siebel Field Service and Ligthouse.
Rhodes is available for iPhone, Windows Mobile, Research in Motion (BlackBerry) and Symbian smartphones. Support for Android devices will be available by end of February 2009.
I just found out about Rhodes, and it looks crazy cool. While I don't currently have a smart enough phone to play with it myself, maybe they'll eventually make it so the thing can target J2ME. (Or, I'll end up getting a smart phone). Regardless, the idea of writing phone applications in Ruby (or another dynamic language) has lots of charm for me, and I've been idly contemplating implementing a interpreter for some small language so that I can do just that on my phone.
In related news, I got to play with my friend's developer G1 this past weekend, and I like. I'm pleasantly surprised at the size and how well it feels. Perhaps I'll get one in a year or so. (And maybe I'll end up with version 2 at that point. ;)