> This is based on what a prototype in JavaScript is. Yes, prototype methods become callable from instances in JavaScript. The "prototype", however, and its close cousin the "constructor" Function (all Functions are constructors in JavaScript) is the closest thing JS has to a "class".

It makes more sense now, although it's questionable whether its a good idea to base the LoopBack on concepts that are not immediately obvious to most developers.

Anyway, I would not think about the rationale behind the naming too much if it was consistent. But it is not. We have `ModelPrototype.create()` and `Model.save()` in the client API, while the server API have `Model.create()` and `Model.prototype.updateAttributes()`. See [crud remote methods](http://docs.strongloop.com/loopback/#crud-remote-methods). That's my biggest issue with the current naming scheme.