I believe object-orientation is dated

I don't know how many advances might be happening recently on some underground Smalltalk mailing-list, but in general, OOP has remained the same for decades.

Does everybody think it's good enough? Does nobody want new features that will make your code more expressive somehow? Watcha think?

>>40
Holy fuck stop posting.

>>41
??

>>34,35
RacialStereotype *pnigra = malloc(sizeof(*pnigra));
*pnigra = { .favoriteMusician = "Lil Wayne",
 .favoriteFood = "watermelonz an da fried chickenz",
 .favoritePasstime = "smokin bluntz wif muh niggaz" };

I believe this is valid C99.

Date my anus

>>44
( ´・ω・) O-Okay. *blush*

>>43
C99 is deprecated.

>FORCED HIERARCHIZATION OF CONCEPTS

Actually it is dumb programmers who think everything should be solved through inheritance. Where I work, almost everybody thinks that way (or just do it without thinking at all).

However I do agree that OO should have more advanced ways to relate concepts. Inheritance and composition are just not nuff'.

And why didn't my quote work, beyond myself being undeserving?

>>48
And why didn't my quote work, beyond myself being undeserving?
This is a text board, so you have to use [quote] and [/quote] instead.

>>49
[quote]This is a text board, so you have to use ... and ... instead.[/quote]

And how did you escape those? Just posting [quote] and [/quote] in the middle of a line will do?

:(

>>49
You funny guy.  _{I KILL YOU LAST}

>>50-52
doyoufeelintimidatedby
power
of
my
BBCode
skills?
Okay, okay, use "> " as the first thing on the line to make it a comment.  Good luck getting multi-line comments, though.

I find that OOP is great for small projects.  If you need a Windows^TM dialog that requires the user to enter some values into text boxes and then click an OK button, OOP is a great way to go.  You can even try/catch/throw some exceptions and bask in the warm and fuzzy feeling of RAII, if you want.

But when a project is large, OOP just becomes a tremendous burden.  It actually makes development slower at that stage of development.  You'll spend all your time in meetings about how the singleton-factory-observer is too tightly coupled with your composite-command-decorator.

>>54

so it is easier to use, but more difficult to write. Makes sense. But what about when you must use what you've already written?

>>55
You lost me.  I said "good for small projects and bad for large projects."

>>56

Well, a GUI library is a large project. But it is easier to use for a small project if the GUI library is object oriented. Do you see the paradox here?

>>54
But when a project is large, OOP just becomes a tremendous burden.  It actually makes development slower at that stage of development.  You'll spend all your time in meetings about how the singleton-factory-observer is too tightly coupled with your composite-command-decorator.

I always felt like OOP was actually interesting FOR large projects and useless for small ones. What do you think is good for large projects like e.g. game engines then?

>>18
PHP may be "a shit" to you but does that change the fact that it's become the ubiquitous language for dynamic webpages?

Many people don't understand the reason behind all of these things they view as flawed. PHP evolved to fit a certain niche and it has evolved well. It was not designed by language experts or theoreticians, but rather by people who had their goal in mind and approached the problem pragmatically. And pragmatism always wins in the real world. In the time it takes for you to find the most "elegant" design for your new web framework and before even writing a single line of code, your competitor has already gotten a site up and running with visitors.

The same argument can be applied to many other things, like the intricacies of the x86 architecture. PHP is not my favorite language, but something has to be said for its practicality and the popularity it's enjoyed. Thus, in much the same manner that I respect and admire the x86 for its longevity and personality, I can do the same for PHP.


tl;dr: Horses for courses, don't let idealism get in the way of practicality.

>>59
Cudder I noticed that you have now added a whitespace between your name and the tripcode, you are no longer silly Cudder.

>>60
The whitespace is sillyness, he is still silly Cudder.
If he posts with an e-mail you will notice that the whitespace is highlighted as well, such is unacceptable.

>>59

PHP may have become the ubiquitous language for dynamic webpages but does that change the fact the it's "a shit"?

Many people don't understand the reason behind all of these things they view as Just Working. PHP evolved to fit a certain niche and it hasn't evolved well. It was definitely not designed by language experts, but rather people with a goal in mind and approached the problem in a Go Horse way. And Go Horse always wins in the real world when the timespan is short. In the time it takes for you to get a PHP site up and running and before even thinking anything (which PHP developers don't do until they bump into a wall), your competitor has already started to think how to approach the problem correctly.

tl;dr: Don't let *blind* practicality get in the way of rational thinking.

but rather people with a goal in mind and approached the problem in a Go Horse way.

but rather people with a goal in mind who* approached the problem in a Go Horse way.

[...] and before even thinking anything (which PHP developers don't do until they bump into a wall) [...]

[...] and before even thinking about* anything [...]

>>60,61
My name has had that trailing space since 2008.

>>62,63
You might want to finish off whatever you're smoking and go for a break before trying to organise your thoughts.

>>35
I think he meant the "method composition" part, which the extent of its flexibility wasn't shown in that example. Its at least more flexible than simple method chaining over a specific object.

(define superfun (compose fun1 fun2 fun3))

(equal? (superfun "input")
        (fun1 (fun2 (fun3 "input"))))
; => #t
In light of the number of parenthesis in Lisp, the benefits of composition is apparent. The problem with "method composition" though is that it assumes prevalent immutable style of OO, but OO is very dependent on ad-hoc conventions.

>>65
If that's what he meant, he's dumb to want it. Function composition makes obvious sense if you look at it from the perspective of data flowing through a chain of mutators, but if you use methods like that, you're just trying to crowbar functional style into OO to the detriment of both.

>>40
Could be done in Haskell:
indie stylish http://joyridelabs.de/
quake3-like game http://www.youtube.com/watch?v=0jYdu2u8gAU

moar http://hackage.haskell.org/packages/archive/pkg-list.html#cat:game

>>67
Haskell is constipated fagshit.

>>68
u mad

How many cons cells would be needed to make seven T-shirts?

>>70
Enough to keep me aroused for weeks straight.

>>70lithp is shit
>>71faggot

>>34

jQueery

>>28
Roles/Traits/Mixins

js has them too
and a lot more useful things coming!
http://wiki.ecmascript.org/doku.php?id=harmony:proposals

Use interfaces as typeclasses (obviously not in java) and read up on multidimensional separation of concerns and its predecessor subject oriented programming.

>>39

game development evolved from object-oriented programming to data-oriented programming years ago.

>>58

entity systems

>>58
large projects like e.g. game engines
Hah!
Game engines are almost by definition not large projects. They get written quickly by a small group of people, comprise relatively little code (except when compared to your factorial or bubble sort implementations, I guess), and don't have to consider long-term maintenance at all.

Game development is easy; that's why there's so much crap out there. If web developers didn't exist, game developers would be the very bottom of the hierarchy.

OOP is seriously retarded, it breeds programmers that all they want to do is obfuscate their code even more, i've been told the perfect OOP code is the one where each method only has one line of code

>>78
You're easier to spot than you think.
First-year students have no business posting on programming boards. Lurk, and don't post until you're in your third year and have come up with an interesting graduation project.

>>79
the fuck are you talking about