2 ms·
Meeting over. Other things not working on GAE, at least in my limited experience: 1) There is no way to run the console, period, which is a nuisance to my ty
by patio11 17y ago
Meeting over.
Other things not working on GAE, at least in my limited experience:
1) There is no way to run the console, period, which is a nuisance to my typical development style.
2) There appears to be no good way to do testing, which is a showstopper for many Rails developers. (I don't do TDD personally so not a big deal for me.)
3) Warble (wonderful software, don't get me wrong) has some performance issues, at least on this computer. (30 seconds to change one line in one file.) That wouldn't be a problem except...
4) ... I can't get GAE to operate locally with Rails, which means development has to be done by edit, deploy, edit, deploy, edit, deploy, which combines all the development speed of Big Freaking Java Enterprise Apps with the rich your-IDE-will-spot-typos-for-you power of Ruby. (/sarcasm)
5) You can't use ActiveRecord on GAE, which sounds like a nuisance until you realize how much of Rails magic depends on ActiveRecord being there. Validations, for example. (This was a major GOTCHA! for us.) I hear this will be mooted with Rails 3.0, which allows DataMapper (which will support Google's data store) to be dropped in in place of AR, but it is one of the major issues making me tell my bosses "The exploratory app was a big success, but the platform is not ready for us to take it to production yet, even though you have one production-ready app sitting in front of you."
- nir 17y agoOnce you're at the capistrano level, deployment is a different game.. I'm talking about relatively small projects (I wouldn't deploy a big project on GAE anyway, if only to avoid the lock-in to Google) I totally agree on most of issues you raise (once GAE Rails would work locally, console, testing etc could be resolved I suppose) - I would definitely not build any size Rails project for GAE right now. But if Rails community would put some work into that, I think it might be a great rapid dev/deploy/scale solution.