3 ms·

If you're focusing on OOJS then you should be focusing on learning other programming patterns in JS, because it isn't meant to be used in an OO context. Look i

by mobinni 12y ago

If you're focusing on OOJS then you should be focusing on learning other programming patterns in JS, because it isn't meant to be used in an OO context. Look into stuff like functional programming, reactive programming, contextual programming. Learn the patterns and learn to apply them in your projects

peterchon 12y ago
I guess that was the problem I faced when I started down the OOJS - what do I exactly use this for? I understand that it's a great way for reuse & extending, but aside from giant applications with numerous developers, is it really useful?
- mobinni 12y ago
  Well with any program language you can solve a multitude of problems I guess what you need to do is start by learning the concepts from the basics http://eloquentjavascript.net/1st_edition/chapter6.html http://eloquentjavascript.net/1st_edition/chapter6.html Also maybe look at larger libraries like underscore, lodash and get acquainted with the programming concepts they apply since they are well maintained libraries. I read you are familiar with AngularJS, get into the source code, understand how the beast works. Get your hands dirty, maybe build something into the angular library itself just to test it out.
awinder 12y ago
This comment is really one of my pet peeves. Javascript is absolutely meant to be "used in an OO context" -- everything including functions have been designed as objects since very early on in the language. It does not implement classical inheritance, sure, but classical inheritance isn't a mandatory design pattern for a language to be considered OO. Functional programming & reactive programming are absolutely valuable, though, and fulfill very real design patterns in Javascript. They're great skills to learn. No one reading this comment should come away thinking that OO is not absolutely important to JS, and that if you try to solve every problem in JS without utilizing it's aspects, you're probably hamstringing yourself without need.

by mobinni 12y ago

peterchon 12y ago

I guess that was the problem I faced when I started down the OOJS - what do I exactly use this for? I understand that it's a great way for reuse & extending, but aside from giant applications with numerous developers, is it really useful?

mobinni 12y ago
Well with any program language you can solve a multitude of problems I guess what you need to do is start by learning the concepts from the basics http://eloquentjavascript.net/1st_edition/chapter6.html http://eloquentjavascript.net/1st_edition/chapter6.html Also maybe look at larger libraries like underscore, lodash and get acquainted with the programming concepts they apply since they are well maintained libraries. I read you are familiar with AngularJS, get into the source code, understand how the beast works. Get your hands dirty, maybe build something into the angular library itself just to test it out.

awinder 12y ago

This comment is really one of my pet peeves. Javascript is absolutely meant to be "used in an OO context" -- everything including functions have been designed as objects since very early on in the language. It does not implement classical inheritance, sure, but classical inheritance isn't a mandatory design pattern for a language to be considered OO. Functional programming & reactive programming are absolutely valuable, though, and fulfill very real design patterns in Javascript. They're great skills to learn. No one reading this comment should come away thinking that OO is not absolutely important to JS, and that if you try to solve every problem in JS without utilizing it's aspects, you're probably hamstringing yourself without need.