5 ms·
Better not define any functions or arrays then, they're objects and that would be "gross"
by shangxiao 12y ago
Better not define any functions or arrays then, they're objects and that would be "gross"
- jackmaney 12y agoBetter abandon any front-end JS, too...
- krick 12y agoActually functions or array being objects internally has nothing to do with "object-oriented" as style of writing code. Here it is about style, which is obviously dictated by Processing (and thus Proseccing.js) being ideologically object-oriented. So, well, yeah, it is quite more object-oriented than "proper" code in js, although I don't see why it is such a problem for the person you relply to.
- deleted 12y ago[deleted]
- shangxiao 12y agoWell actually it does. Every time you do an someArray.push(val), that's "object oriented as a style of writing code". If you're referring to the style in the article (ie the Java code), well that's classical object oriented.