I find the App Engine docs pretty good too. Some things could definitely use improving, like documenting all the rates, limits, quotas, deadlines, etc..., in one spot so we can search / find info (including low-level stuff), but they are otherwise ok.
I also find that if you stay *high* in the SDK files (ie the public interface) it is not too bad -- and the doc strings are good. Just don't dig in; it gets tangled up fast. The gdata docs / api are a different story -- complete and total mess, along with a disaster of an API to go with it! But, that's not related to App Engine. Robert On Tue, Sep 20, 2011 at 14:45, Jeff Schnitzer <[email protected]> wrote: > Wow. I've found the GAE docs to be pretty nice. What some pain? Try > the docs for: > > * Amazon Elastic Beanstalk > * Paypal > * Google Checkout > * Amazon Payments > * require.js > > ...just to name a few that have given me grief lately. Paypal gets > the poo-colored star here. They are truly a testament to how hard it > is to unseat a market-leading incumbent, even when they suck. > > Jeff > > On Mon, Sep 19, 2011 at 8:48 PM, Ryan Mattison <[email protected]> wrote: >> For being geniuses, your documentation and organizational skills are >> less than desirable. You choose to take on multiple IDEs/environments >> and release them untested. Try picking one, we all have Linux, Mac, >> Windows. State the person that wrote this documentation is on XXYY >> version xy, so it must work as he expected (we are testing other >> environments, but we know this one works!). I've developed against a >> load of sdks web, mobile, data, os, windows etc etc, mostly because I >> like to have an extremely good time,can't pull my life together, need >> money and lack the overall skills to be a engineer. One thing is >> certain though, I would rather jab my eyes out then work through the >> next Google project. I have to be employed in America, why do you >> have to make it painful. Not everyone gets off on digging through >> scripts, open source code, and logs to decipher why this pos decided >> to lock x file and not rebuild it & write nothing to a log etc. Some >> of us want to build something cool and go to the bar. >> >> Lastly, why the verbosity? Clear & concise patterns & code never seem >> to be the aim. Its not like the code needs to be clear it'll take a >> pick ax to get through a relatively new Google environment anyway. >> You may as well finish it off and let developers type less. >> >> Composite, C >> Calendar, Ca >> >> Let me imagine I got the chemistry degree I should have. >> >> Alright, better now .. back to jabbing my eyes out. Your responding/ >> discussion skills are way above bar though, so that is good !~ >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" 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/google-appengine?hl=en. >> >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" 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/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
