Dorian Smiley
2 min readMay 4, 2021

--

The tone in the comments section sucks. Good article. OOP provides a ton of useless decoration and ceremony and there are plenty of well respected engineers who agree with that statement. Mixing state with your functions is an entire debate the Haskell and Clojure community would love to have with anyone who's willing to engage in thoughtful discussion. Personally I'm not a fan of writing code that doesn't do anything, and if you understand how OOP works in JS you quickly realize that is a large portion of the code you are writing. Javascript was not an OOP language as designed. The history of how OOP was thrown in is a fact, not disputable IMO. The language has since evolved though and the syntax sugar has made it easier for developers in an OOP style. But it still lacks many features of a true OOP language not the least of which are proper member scoping, packages, and encapsulation. In fact, I'm really not sure what this pile of dog poo should really be classified as, which largely explains why tools like React and TypeScript are so popular. Programming in a procedural or functional style is just as valid as adopting an OOP style in the Frankenstein monster of a language. Personally, I think it would be interesting to observe the bug reports among those three groups. I'm pretty shocked engineers would actually defend the OOP like aspects of the language by holding up actual OOP features as a defense not realizing the irony. I realize that is debatable, but I don't think many people making these comments realize that as well. Personally I'm moving away from Javascript and embracing Haskell and Rust. I don't always program in Javascript, but when I do I prefer TypeScript (and yes I know it's. a superset and that's the point).

--

--

Dorian Smiley
Dorian Smiley

Written by Dorian Smiley

I’m an early to mid stage start up warrior with a passion for scaling great ideas. The great loves of my life are my wife, my daughter, and surfing!

Responses (2)