Grails 1.1, Hudson and Maven...[Redacted]

Posted on March 17, 2009

So, I recently created a new project based on Grails 1.1, which I needed wrap with Maven. Grails 1.1 IS ready for prime time. With the maven-grails-plugin I was able to simply call ‘mvn install’ from my Hudson CI environment – even with no Grails 1.1 installation on the CI server. Very, very cool. Great work from the Grails camp!

[Note: I had to backtrack on my previous post…sorry.]

Atom Versus ARM, huh?

Posted on March 17, 2009

As the Netbook market continues to evolve – so has the technical specifications that drive the smaller form-factors and architectures. I actually don’t believe that ARM has any place in the Netbook market.

Here’s why. I spend a considerable amount of time developing for the Gumstix platform. The Gumstix runs OpenEmbedded, a cross-compile environment for many embedded processors – most notably, the ARM family. Without going into great detail ARM != x86 (Intel stuff). The cross-compile dance is required to build all the Linux pieces specifically for the ARM architecture on a (normally) x86-based machine. While OpenEmbedded supports many of the pieces, that normally doesn’t cut it. If it is not a supported package the process (project creation, make manipulation and cross-compiling) is just gross. Now, coming from an embedded background I’m used to that. The Linux community in general is not. I can’t speak for the Winders folks, but guessing not. :)

Sure, the ARM platform will get you lower power consumption/longer battery life. But, at the cost of CPU/RAM resources, and the above mentioned architecture mess.

To be honest I’m not sure the ARM even has a place is micro devices like the Gumstix.

The fit-PC2 shows just how close we could be from a form-factor perspective to the Gumstix with an Atom-based(x86) processor and 1GB of RAM. Shoot, just get rid of the connectors and we’re damn close.

The fit-PC2 runs a full-blown Ubuntu environment, which means no cross-compiling.

The downside is that the fit-PC2 requires 12V and consumes ~6W. For many applications that may just work…leaving the door open for the ARM platform. But, I just have to wonder how long before we see 1+GHz Atom-based platform running off of 3.3-5v at 1-2W. Lights out ARM.

But, the ARM fights back. The BeagleBoard an almost viral phenomenon parented by TI is proving that the ARM is a valid, general purpose platform.

Again, I’m waiting with intense curiosity…I have to believe Intel is hard at work (probably with Apple’s interest in mind) on a super low-power high-performance processor that will bridge the gap and extinguish the need for cross-compiling.

All this stuff said, I do understand the deltas between the truly embedded architectures. I’m just a software engineer who appreciates the OS and application side of things and really want to see a simpler means for eliminating the void between desktop and mobile platforms.

GoDaddy Email + PGP = NoDaddy!

Posted on March 02, 2009

After way too much time spent by me and a PGP support guy I finally came to the conclusion that GoDaddy was mucking with the SMTP side of things – to the point where I couldn’t send an encrypted email. I’m already a tad bit disgusted with GoDaddy’s “Girls Gone Wild” marketing slant. So, this new revelation that there is some inherent need to not allow me to send encrypted emails is a bid awkward. Remember just because you may being using SSL to send mail, it is only SSL’ed/encrypted between you and their relay. (I could be wrong here, and it wouldn’t be the first time – but, I’m just too lazy to find out. Plus I’d like to think there is more to me wanting to leave GoDaddy besides their sleeziness.) The problem is that the PGP Desktop/email proxy wasn’t able to do its thing based on the email configuration. I happen to be on a Mac and using Apple Mail, which at first I was willing to drop the blame on. But, after switching to a new provider the PGP Desktop client configure everything transparently with no issues. It did do a number on my Gmail configuration – disabling TLS there. But, all I had to do was turn it back on, and disable the PGP auto-configure option.

So…if you are hoping you’ll be able to sign and encrypt emails for a domain hosted through GoDaddy – get ready for a battle, or a switch.