Recovered from the Wayback Machine.
This is a good point. If you’re only using Prototype to access a page element or make an Ajaxian server-side call, you’re not using Prototype to the fullest, and you’re better using your own homegrown.
I agree with Ajaxian, though, in that there is documentation on Prototype, though the creator of the library seems to be reluctant to make this known. Where I don’t agree with the writer, Rob, is his statement:
…although I’m disappointed to see that Sergio hasn’t updated his excellent reference since May, there are still so many fantastic howto’s and tutorials written using Prototype. Plus the books out now that base much of their code on Prototype.
I also dig into the libraries, exploring the code, and that includes Prototype because it does have some very clever implementations and nice use of JS. Still, I don’t just write “we’ll use Prototype for this” without explaining why. I don’t know of a lot of other Ajax books that are completely dependent on Prototype, either. Too much is changing in this environment to make folks dependent on one library or another.