4 ms·

s/bad/unfashionable

• nathanaldensr 8y ago
  Except it's not unfashionable. It's used by millions of programmers who just want to get stuff done. It's used by thousands of companies who don't really care how the native instructions are eventually generated. It's used by individuals and teams, application developers and library authors. This premise of this video is flawed from the beginning and the whole thing is basically a gigantic straw man.
  • mrkeen 8y ago
    He has reduced OOP to polymorphism/encapsulation/inheritance. Is that what you mean by the straw man?
    • 0x445442 8y ago
      Not sure if nathanaldensr means that but that's what I would say is the straw man. Also, it's been my experience a lot of developers have a lot to learn about OOP principles. The most common OOP idea that's seemed to have been lost is asking an object to reason about its current state. If I had a nickel for every time I see code like below... String fooJson = new Gson().toJson(foo, Foo.class); or Double totalTax = TaxHelper.totalTax(orderItem.getCityTax(), orderItem.getCountyTax(), orderItem.getStateTax());
    • peteradio 8y ago
      He specifically says inheritance and polymorphism are irrelevant in the video. His problem is with poor encapsulation which is not specific to OOP.