I forgot to mention that you could pull out of Heroku/Amazon and just use Postgres locally, but GAE using Big Table means that you can't pull out and locally install Big Table. That's another problem if you have any concerns about committing or re-working down the road map for a project.
On Apr 9, 8:32 am, justindz <[EMAIL PROTECTED]> wrote: > Amazon offers platform in a generic sense. GAE offers web app > platform in a more targeted sense. Heroku adds web app targetting to > Amazon. So, once Ruby support is implemented on GAE, I think the > question would come down to: > > - Library support. > - Database model. > - Documentation, support and useful but unobtrusive features. > > Compared to GAE Python, Heroku offers actual library support although > with some limits (I still don't have ferret working, e.g.). > > On database model, Big Table is non-relational and so that might not > be appropriate for all projects or at least for some scale of projects > might present a barrier of entry. > > Heroku is *very* thin on documentation, tutorials, FAQs and other > content that would facilitate development and point out the > differences between cloudware capabilities and desktop capabilities. > Ferret is a good example of where there are clearly differences and > where they are under-explained. From my viewpoint (because I'm not a > genius coder working full time on my app), the post that ferret can > now be used was insufficient given that it's successful use isn't > obvious from purely non-cloudware-based instructions. GAE is rumored > to have the exact same problem: insufficient documentation. However, > if Google applies resources to create documentation en masse, > reference implementations, tutorials and other things then they may > ultimately have a lower barrier of entry for the part of their target > audience who are not already superb hackers. > > In my estimation, given two cloudware services that target web apps > and support Ruby and RoR, the "winner" will be at least in part > determined by who does the best job with that list. Of course, this > is beta, but beta these days is where the precedent for eventual > service level is set. > > On Apr 8, 9:47 pm, ChessMess <[EMAIL PROTECTED]> wrote: > > >http://smoothspan.wordpress.com/2008/04/08/why-google-and-amazon-are-... > > > "Personally, I think Google could acquire Heroku and Zend and > > immediately pick up Ruby on Rails and PHP. If I were at those two > > companies I would be eagerly trying to have the conversation. I would > > also be calling up Amazon. Heroku is Ruby on Amazon already, and > > would instantly give Amazon parity again with Google App Engine only > > with Ruby instead of Python. That would make a wonderful return shot > > from Amazon." > > > Good thoughts I'd say. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
