Rich Skrenta: AppEngine - Web Hypercard, finally
skrenta.com
skrenta.com
Although google's appengine is more open, a lot of its key components are proprietary and can't be easily rebuilt. So while hypercard and appengine are both wonderful technologies, I believe people should prefer something more open. This allows you have an out in case google stops supporting appengine or does something that prevents you from using it effectively.
Its still up to the diligence of the people who write the app. The problem with hypercard, was that the people using the app were the ones that created the cool stuff, and the people maintaining hypercard wouldn't/couldn't keep it going for them.
I'm waiting for Amazon to respond with something similar. Just to get an application up and running on Amazon seems to involve delving into message boards (I have EC2/S3 accounts but it's learning how to port my web app is not a priority at the moment)
The premise of EC2/S3 is that you can ask for services/CPU on demand - however Google with AppEngine has significantly lowered the barrier to creating a scalable web app (by handling scaling for you, once you write to their APIs and give them your code [another issue]). Not everyone wants to be an Erlang expert and roll their own scalable code.. (some people just want to be able to build a cool popular app and outsource worries about scaling).