Every now and then, some really cool pops up on my radar. In this case I saw this article at Info World about Google’s Android Open Accessory Developer Kit (ADK).
I’m a bit of a do-it-yourselfer, so when I saw this, I just had to tell you about it (yes, all three of you who read this blog).
I can envision a number of really cool electronics projects that I could do with this. Of course, I’ll need to invest in an Android Tablet (but I was probably going to do that anyway), but the ADK is free to download, and there’s no annoying developer program to join.
Cool. Way cool.
Okay, that’s a little dramatic, I admit. But as enterprise architects don’t we need to know what other options our customers and end users are potentially looking at?
I saw this article at Info World, and it made me wonder: is Mono a viable enterprise application platform? Many seem to think it is, but as the article points out, its future is uncertain. Microsoft has committed through its Community Promise not to prosecute anyone who use the ECMA 334 and 335 standards (which define C# and the Common Language Infrastructure – CLI – respectively). So, you’re probably okay to use Mono, for example, without fear of Microsoft claiming patent infringement down the road.
But so what? So let’s suppose Microsoft will play nice (and that’s a potentially big assumption). Is Mono still a viable enterprise application platform?
I have to admit, I really don’t know much about it. Which is why I’m posting this. I would like to hear from you: The experts of Java Enterprise Open Source Application Architecture. Do you know your enemy? I mean, do you know the other enterprise application platforms (including Mono) out there? Should we care?
What do you think?