This argumentation is compilation of unjustified and demonstrated claims. It really doesn't help in understanding the author's point.
All evidence points to OOP being bullshit (2013)
11–20 of 126 posts
Re: All evidence points to OOP being bullshit (2013)
#12What probably scares me most is, that managers think OO is in general a wonderful best practice you need to have in the company...
Managers who think, there is a silver bullet, always scare me!
Re: All evidence points to OOP being bullshit (2013)
#13Depends on how you use it, of course. Libraries make wonderful showcases for OOP strengths - I always like to give Java Collections as an example. But if you actually build your application code as OOP... well, I might privately think you deserve everything that happens to you because of that. I think education carries most of the guilt for this. The typical examples given in OOS classes are stuff like Car is an ance…
This example looks bad to me -- shouldn't it be that car, truck and sports car have (at most) a common vehicle superclass?
Re: All evidence points to OOP being bullshit (2013)
#14Can someone make a chrome extension to filter out the OOP vs FP articles on hacker news? I mean, how many more articles do we need? Is there anything new? Yes, FP is cleaner. Yes, OOP is useful for things like plugins. Yes, favor composition over inheritance. Yes, FP is impossible to read. Yes, immutability has its limits. Yes, Yes, Yes. Enough already.
Even FP needs some mutability when it comes to databases and user input.
let's consider a website you would need io -> handler -> database so the io and the database is a mutable connection between the handler that by itself could be fully mutable.
Mostly I think most problems of OOP and FP are solved by Reactive Streams since they encourage small units and each unit could be either programmed with OOP or with a Functional Style. This solves a lot of things.
Btw. I'm mostly writing Scala and I love it, still I use some Objects or sometimes use Java. Golang or other stuff. It mostly depends what I'm doing.
Re: All evidence points to OOP being bullshit (2013)
#15"All evidence"
https://xkcd.com/605/
Re: All evidence points to OOP being bullshit (2013)
#16What probably scares me most is, that managers think OO is in general a wonderful best practice you need to have in the company...
What scares me more are managers who think dogmatic adherence to "best practices" is the only way to be successful.
Re: All evidence points to OOP being bullshit (2013)
#17> Probably as good as any other programming paradigma out there.
I take offence with postmodern relativism. Not every paradigm is created equal (and for the record, black culture is less "good" than white culture. Come on, "acting white" because you have good grades?).
The way to get better as a professional is to analyze various ways of doing stuff and find which is better and how much of it you can use. This article does exactly that.
Re: All evidence points to OOP being bullshit (2013)
#18I found it ironic that he used a quote from Alan Kay to attempt further his point that "object-oriented programming is bullshit"
Re: All evidence points to OOP being bullshit (2013)
#19Depends on how you use it, of course. Libraries make wonderful showcases for OOP strengths - I always like to give Java Collections as an example. But if you actually build your application code as OOP... well, I might privately think you deserve everything that happens to you because of that. I think education carries most of the guilt for this. The typical examples given in OOS classes are stuff like Car is an ance…
> But if you actually build your application code as OOP
> Beans and Entreprise Java
I don't know. Netflix is built on Java, using OOP. It works well for them. Windows is built on OOP, quite a big application and works.
J2EE has its problems, but it also gives you a lot of functionality. Reusing methods is nice, but developers on projects with very complex business rules (does not equal simple, but large scale projects!) don't worry that much about flexible methods as they're experienced enough. Distributed transactions, session replication, etc. are slightly more important. J2EE gives you all that by default.
(And I really don't like EJBs and this kind of stuff, but don't mix up two very different levels of problems.)
Re: All evidence points to OOP being bullshit (2013)
#20This argumentation is a compilation of unjustified and demonstrated claims. It really doesn't help in understanding the author's point.