About the cost I completely agree with Simon Knott that bad system design 
can cause creeping costs you eg. having a cron job every 5 seconds for what 
can be batched in a daily cron job would significantly increase your costs 
at no particular gain in efficiency so I too think that some of us who saw 
creeping costs and creeping CPU used the GAE environment in a wrong way and 
we had to unload some of our scripts such as cron jobs every 5 seconds not 
thinking about number of reads/writes/creations. 

Which was good since the pricing force us the write program 
cost-efficiently - otherwise we can't afford running the apps.

So I think focus on a particular technical problem and solve it rather than 
bringing everything up under "unhappiness". 
Work for a specific issue, debug it, make a proposed solution while you 
wait for the solution and then you'll have 2 solutions. 

I found I could solve all problems with app engine though in a python way 
sometimes there seems to have been one way only to solve it well (which was 
webapp2 + wtforms + jinja2 for me.)

But I like that you bring this up since I too have been frustrated with 
lack of "real" system functions such as eg. backup where phpMyAdmin you 
just push the button and you get a backup in zipped SQL of your whole 
database and no need to worry. App engine severely lacks a good backup 
system, we have to write our own backup system and this is not application 
development, it's developer tool development which is OK and fine solving 
it once per environment. Solving same problem for every app (backup, file 
system, static files, upgrading to python 2.7 with all its migrations..) 
should be done once for the whole platform like making one good backup 
function that works for the whole platform or just an XML export of the 
datastore if they can't other format.

My bottom line is that I came here to do application development and found 
myself implementing development tools such as backup and file system. 

That said, Google App Engine has enough advantages to still be the best 
platform and the best development environment. I just wish it was a real 
system that came with an export / import function and backwards 
compatibility and lots of ready-made builtin solutions for CMS with 
plug-ins etc like regular LAMP has. Regular LAMp has, to be fair, at least 
5 years head start of app engine so to be fair we have to wait some time 
for app engine to mature and all problems will have been solved. In 5 years 
time, I believe app engine will still exist and that nobody more worries 
about their python 2.6 to 2.7 migration.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/XZyCMPmm7eMJ.
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/google-appengine?hl=en.

Reply via email to