Java: Coming Soon to Google's App Engine

35 thoughts on “Java: Coming Soon to Google's App Engine”

  1. Hey Om,

    I would suspect it’s either using Dalvik or V8. I would actually hypothesize it’s V8 – Dalvik has been tuned to run on mobile hardware, V8 has been tuned and designed to run on standard PC hardware.

    Also, the guy that designed V8 at Google worked at Sun and was lead engineer on designing HotJava, one of the first JVMs. I wouldn’t be surprised if that’s how Python is running too, on V8.

    I think a more accurate story description would be Google to support Java Syntax on AppEngine, just like it supports Python Syntax.

    1. Dude, java & javascript are different (You can read up on their origins in the late 90s and understand why their names are similar).

      V8 is for javascript. Dalvik is for Java.

      -jb

    2. I know JavaScript and Java only share a name. But V8 is a high performance Virtual Machine, not just a little JavaScript engine.

      Do you really think Google would spend 2+ years developing a measly little JavaScript Engine?

  2. I dont think GAE will be using Dalvik as its slimed down jvm for mobile devices with serious limitations for server side apps ……..Instead google has pushed for realtime Resource Consumption Management API in java as standard (Java Specification Requests 284 )in java for managing apps running in same jvm (this would allow for better shared hosting java apps on server ) ….you can read more about this JSR 284 at http://jcp.org/en/jsr/detail?id=284

  3. I thought they would release PHP first. Python is a mess, Java is strong in the enterprise scene but not in the cloud. PHP is the most popular development language for internet applications, huge developer base, simple, intuitive. I wasted too much time figuring out Python obscure coding techniques writing my Goole app engine applications, I hope PHP is next.

  4. I don’t know how there stack works but I am guessing the only reason that java is next is because most of the libraries were already in place. Php would start to trouble ec2 but their non sql data storage will never compete with mysql as it is. Developers who know php will want mysql. Ms are suppling sql

  5. I don’t know how there stack works but I am guessing the only reason that java is next is because most of the libraries were already in place. Php would start to trouble ec2 but their non sql data storage will never compete with mysql as it is. Developers who know php will want mysql. Ms are suppling sql
    P.S. – Sorry, forgot to tell you great post!

  6. I’m wondering what their exact terms of service will be… It is their general terms where they reserve the right to use your data to better profile you and your users? As you put your application source and data into their cloud, can you ever fully remove it or protect it? Will they track your application usage and use that data? And will Google try to control the kind of applications it will host (like they don’t allow apps into their Andriod market-place that don’t comply with their cellular partner’s ToS). Google is all about maintaining control… too much so for my taste, I suppose. With the support of Java and the introduction of an Eclipse plug-in, it’s starting to catch up with AWS (and related tools) – just with a whole lot more limitations.

  7. I can’t believe GOOG released App Engine and GWT *without* making sure that they would work together. Who is running that shop??? At least search works!

This site uses Akismet to reduce spam. Learn how your comment data is processed.