4 ms·
I definitely wouldn't take this for granted. All it means is that, right now, there are internal resources dedicated to improving the platform's language suppor
by obviouslygreen 13y ago
I definitely wouldn't take this for granted. All it means is that, right now, there are internal resources dedicated to improving the platform's language support. Those that make this largely unsupported assumption will be the most irate and in the worst position if Google drops the platform at some point (not to mention this platform is horrible in terms of proprietary lock in).
- markdown 13y ago> if Google drops the platform at some point That's a little too far-fetched for me. GAE isn't in the same category as end-user services like Reader or any of the other apps they've dropped. I don't expect them to run it forever, but I trust them enough to believe that if they ever decide to pull the plug, they'll give us a fair bit of warning (half a decade?). They're not stupid, and they're not suicidal.
- bink-lynch 13y agoI too was concerned about lock in; however, it is really not that bad. I have been on AppEngine from the moment they supported Java. I created an abstraction layer between my program logic and whatever services it uses. This has allowed me to take the exact same compiled jars and run them on AppEngine using the datastore for persistence or in some other servlet container using SQL Server for persistence. Just one additional advantage of using this approach is that I can use text files for testing and the program logic doesn't know the difference. That's how I got rid of the lock in issue.