On Mon, Sep 26, 2011 at 3:59 AM, Alan Williamson (aw2.0 cloud experts) < [email protected]> wrote:
> This has taken the shine away for me personally for GAE. I am in two > minds as to whether or not I recommend to the steering committee whether we > should just drop support for it and concentrate on the core engine and > desktop launcher. > Totally understand the conundrum and my brain's split on it as well. On the one hand I'd hate to see it go away because in the abstract it's a slick solution and potentially a great way to promote CFML (which is what we were trying to do with the open source Enlist volunteer management application we started at OpenCF Summit last year), but in practical terms when you have deployed apps breaking when Google makes an API change, and if it's a constant headache to keep up with the changes, I get the notion of wanting to focus on the core engine instead of dedicating time to trying to hit a constantly moving target. I suppose it boils down to whether or not the GAE API might stabilize a bit now that they're out of preview mode with it. Stuff to ponder. -- Matthew Woodward [email protected] http://blog.mattwoodward.com identi.ca / Twitter: @mpwoodward Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html -- official tag/function reference: http://openbd.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
