Stumble upon this blog post via Google Reader today, and I don’t think it has received much attention. Michael Podrazik wrote about his prediction that Java will be the next Google App Engine Language. Quoting from Michael’s prediction:
So how reasonable would it be to offer a hosted Java environment? While almost any hosting provider currently gives you the option of running PHP, lots of ‘em give you Perl, etc. virtually nobody except boutique hosting providers let you run Java. There’s a good reason for this. First of all, Java is an enterprisey language and the apps that use Java on the server side are not especially well suited to run in a shared environment. Secondly, even if the market existed, there are technical limitations that make running Java in a shared resource pool problematic. … The fact that you can’t just run a Java program using an Apache module or through CGI, and the fact that there tends to be a mismatch in the skill sets that *nix ops people usually have and the skill set required to effectively manage a Java app just further muddies the waters.
This echoes the sentiments expressed Deployment is Colonization but also brings up an interesting possibility. Could Google be getting ready to solve the long-standing issue with Java application hosting by doing something revolutionary?
Podrazik goes on to predict that Google will release a reduced capability JSE and do something along the lines of Android (Dalvik) and GWT’s reduced Java API.
All eyes toward Google I/O.
(C’mon the last post was my JavaOne session notes? Where’s everybody at?)