There are several open-source efforts to get a drop-in replacement. [1] It is likely that this will happen before Google open-sources the code. Still, it would be great to get a commitment from Google that, at some specific future date (say, in 7 years) they'll open source their current code. (That is, code that's 7 years old by then - without the intervening improvements. The open source community could take it from there.)
But remember that they make heavy internal use of Bigtable and other bits of code, far beyond app engine. App engine is a relatively peripheral business for them, and probably does not pull the clout to get all that up-to-date code open-sourced in the forseeable future. That's why personally I'd be happy to settle for a commitment to open- source old code later. [1] http://blog.notdot.net/2009/04/Announcing-BDBDatastore-a-replacement-datastore-for-App-Engine is not the freshest blog post, but it covers a number of the efforts. On Mar 21, 4:28 pm, Josh Rehman <j...@joshrehman.com> wrote: > It would be great to run my own app engine, both for development, and > for production. Writing apps for a proprietary platform like GAE ties > you to the platform, as I'm sure Google is aware. So, is there any > chance the App Engine will be open-sourced such that it can be run on > non-Google hardware? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
