I think the big diff is that prototypes can fully act more as global methods upon each data type; a method of a property doesn't makes sense in C as it does in JS. That you can upgrade your existing bundle in a different place entirely is a powerful possibility, and one that must be used responsibly.
i think that to get going, look into turning some of your repetitive procedures into prototype methods. for example, you might have to calc an average often. Turn your avg-finding code into an Array prototype, and you can replace several repetitive procedural code sections with just one-line of code performing just one-call.
I find that this allows more design flexibility than having to decide every capability of every object and property up-front. Furthermore, most of the generic prototypes you create for built-in types like String and Array can be cut-and-pasted into any project, without having to rename any handles or pointers, saving a TON of time.
in short, don't rush; this stuff is complicated and takes a while to sink-in. I think that beefing up the built-in gives you a lot of custom power without forcing OOP conventions down your throat.
i'd throw some examples your way, but im supposed to be getting ready for a valentine's dinner... cheers!
BROWSER STATS [% share]
(2013/10/31) IE7:0.5, IE8:8.6, IE9:5.3, IE10:12.3, FF:17.7, CH:41.8, SF:8.1, MOBILE:20.4