I did not imply that OO was absolutely bad. It's what people are doing
with it. It's been a plague for the last 10 years. The rope is long and thick,
more than enough to hang yourself in several reincarnations.

As far as using OO to represent the real world, it's a mistake.
Things are not as straight forward as they look like. Modeling the surface
is most of the time wrong not withstanding the time it can take to model
everything you can see because you did not think about the essential
stuff you will really need to solve the problem at hand.

I saw enough insane models were the business "model"
was so utterly complex that it made any system improvement a Titan
task. Generality gets hit badly in many OO designs.

You can build an 8 mille bridge with Lego bricks but it's not optimal.
There are better ways. We are not ants or termites.

Luc P.



> Relevant? Well it is always nice to find different articles that are
> bashing on the issues that could appear from badly designed OO programs if
> you want to get Clojure into consideration in your organization.
> 
> I don't support that OO is bad. It is just complicate to constrain yourself
> from making it overcomplicated because after all they teach us that it
> should be representation of the real world and sometimes the world is scary
> and crazy place...
> 
> 
> 
> 
> 
> Best regards | Med venlig hilsen,
> 
> KALINA TODOROVA
> T: 0045 52 64 93 73
> E: ad...@ki6i.com
> 
> Frederikssundsvej 194 2 1
> 2700 Brønshøj
>   <http://www.facebook.com/ki6i.kali> <http://dk.linkedin.com/in/ki6i90>
>   <https://twitter.com/#%21/ki6i> <http://blog.ki6i.com>
> 
> On Sun, Sep 14, 2014 at 8:01 PM, Softaddicts <lprefonta...@softaddicts.ca>
> wrote:
> 
> > I think this article is partly true, at least in the OO world we know
> > today.
> >
> > I dealt with a number of OO based commercial softwares in the past 10 years
> > that used abstractions that were at best annoying, at worse made the
> > internals
> > obscure up to a point where you wondered if these were added only to insure
> > some job security to the "experienced" anarchitects that created them

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to