Comments on: Questioning OO

By: Matt Follett

Matt Follett — Thu, 26 Aug 2010 15:19:38 +0000

Any one paradigm will have its limitations. Languages that can support multiple paradigms, even somewhat loosely, seem to be a better solution. Alternatively, environments that support multiple languages of different paradigms being easily combined are another solution.

By: Brian Bay

Brian Bay — Tue, 23 Mar 2010 19:51:36 +0000

I read this post and I found this quote from Joe Armstrong ( creator of Erlang ).. it struck a chord with me, so I thought I would share it…..

“I think the lack of reusability comes in object-oriented languages, not in functional languages. Because the problem with object-oriented languages is they’ve got all this implicit environment that they carry around with them. You wanted a banana but what you got was a gorilla holding the banana and the entire jungle.”

By: Moandji Ezana

Moandji Ezana — Thu, 11 Mar 2010 23:19:28 +0000

@Tasos Zervos
Yeah, I hope modules turn out to be as useful as everyone is hoping they’ll be.

By: Tasos Zervos

Tasos Zervos — Mon, 08 Mar 2010 11:00:05 +0000

@Moandji Ezana
I believe this is a problem as any real-use component/library/etc. will comprise of multiple packages since many times packages are used to organise layers/sub-components/etc.
What we need is a higher level concept to packages. This is most likely “module”; coming with JSR294.
My understanding is that with this JSR a new access modifier will be added in the language – module.
http://openjdk.java.net/projects/jigsaw/doc/language.html

By: Moandji Ezana

Moandji Ezana — Sat, 06 Mar 2010 23:38:21 +0000

@Ed Kirwan:

“With the latter, indeed, I’d have some sympathy: a recent survey*** of Java projects on Sourceforge showed that most projects leave three classes public for every private class they define in a package.”

Maybe package-private classes aren’t used a lot because they’re too restrictive. I try to use them as often as possible, but I often find myself wishing it were possible to make a class visible to its package and all subpackages.