Well if you're really that curious, I haven't touched Java since college in like 2012.

Also, maybe read back over my original comment that you so eagerly misinterpreted. Everything I said was language agnostic.

I'm not sure what your goal is other than to look obnoxious honestly. If you want a recap on what I'd originally said it was to use classes where applicable and functions where it makes sense. There is no class concept in pure functional programming. And a function must be attached to a class (aka method) in pure OOP. In other words, nothing I said was wrong soooo what exactly is your problem here?

And yes I do want to call it a method because that is what it's called.

Java has lambdas, cool? I haven't used it in years so I'll concede this is news to me but it's not a secret it was based on OOP. I think you're laying so hard into this one thing to save face when really you couldve just deleted your original comment.

> Also, a function is a method you dimwit

Yes a function... attached to a class...making it a method. Maybe lay off the name calling if you don't follow on the semantics

And as for linq in C# and lambda in java, congrats, you've successfully described a multi paradigm language. Spoiler alert: almost all of them are

Oof you should Google before you comment. OOP and functional programming are design paradigms. There are languages that only supports a single paradigm like java. Also a Class "function" is a method...yup. unless you mean a static method but still a method. What I'm describing is a multi paradigm design (if that's the right term) and how to determine what to use.

So yeah, I'd say you clearly don't understand. Here let me Google that for you

https://www.imaginarycloud.com/blog/functional-programming-vs-oop/

https://stackoverflow.com/questions/155609/whats-the-difference-between-a-method-and-a-function

> I think a functional codebase could be successful if architected intelligently and thoroughly beforehand.

And there it is. This OOP vs functional argument is idiotic. The reality is either can work assuming they were well architected and implemented cause that's all that matters. So many think it's one or the other instead of using both and determining which with common sense.

Is it a thing that has attributes? Boom class. Are you trying to perform some sort of action? Boom function. Is that action coupled to retrieve or update the remote state of the class? Then you have a method. Can the implementation of the method be reused or broken out into smaller reusable pieces that are easier to test? Back to function(s) but maybe call it/them within a method to improve usability. If every engineer followed this simple flow life would be so much easier