ryankinal

4 ms·

1. 1.▲
   by ryankinal 14y ago

   I disagree. I think the prototype pattern is quite well designed. It's just not well-supported across browsers. The Pseudo-Classical/Constructor pattern is the one that's broken.
2. 2.▲
   by ryankinal 14y ago

   Good workaround! I like it.
3. 3.▲
   by ryankinal 14y ago

   Indeed. I think I'll be updating the article to include your modifications. Thanks (and how should I attribute? ef4 on HN?)
4. 4.▲
   by ryankinal 14y ago

   A programmer trained in classical (as opposed to prototypal) languages. Languages like C++, Java, and PHP are classical. JavaScript and Self are prototypal.
5. 5.▲
   by ryankinal 14y ago

   Yes it should! Good catch. (This has been updated)
6. 6.▲
   by ryankinal 14y ago

   Simple, sure. Well-designed? Nah. And keep in mind that this is a "classical" system tacked on top of a prototypal system. Not exactly elegant.
7. 7.▲
   by ryankinal 14y ago

   I'm not sure it's exactly a problem. This will happen no matter which OO pattern you're using. It's just something you need to be aware of.
8. 8.▲
   by ryankinal 14y ago

   That is an excellent point. I mean, ideally the constructor doesn't have side effects, but this is a good defense against those that do.