The documentation isn't *that* bad (but it isn't good either). But couple that with the fact that it isn't obvious how to accomplish even basic tasks due to really weird (or just different) naming conventions and it does make for quite the frustrating experience.
I wrote a couple of basic apps (just to see how the platform looked/worked) and it was very underwhelming. I imagine that big companies that can get directly in touch with core developers will be able to make great applications. But us hobbyist programmers don't stand a chance...which is interesting since that is where Google earmarked money.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
Whiny developers expecting a 1.0 release to be perfect. Go back to writing Facebook enhancements!
Writing code is hard.
Learning a new framework is hard.
Learning a new framework without good documentation is frustrating.
Learning a new framework that is buggy without good documentation is demoralizing.
Hopefully this negative exposure will help google get it together.
Agree with gb.
The documentation isn't *that* bad (but it isn't good either). But couple that with the fact that it isn't obvious how to accomplish even basic tasks due to really weird (or just different) naming conventions and it does make for quite the frustrating experience.
I wrote a couple of basic apps (just to see how the platform looked/worked) and it was very underwhelming. I imagine that big companies that can get directly in touch with core developers will be able to make great applications. But us hobbyist programmers don't stand a chance...which is interesting since that is where Google earmarked money.