OOP Considered Harmful

Object-oriented programming encourages over-engineering, leads to slower code due to virtual lookups, and it doesn't solve any problems.

Objects are fine, but don't overuse them.

Functional programming encourages over-engineering, leads to slower code due to virtual lookups, and it doesn't solve any problems.

Functions are fine, but don't overuse them.

>>2 HOW DO I TROLL?

But really, the greatest problem of FP is that it is far too academic for a real world. No, wait. It ain't a problem. It's a bliss.

>>3 HOW DO I TROLL?

But really, the greatest bliss of FP is that it is far too academic for a real world. No, wait. It ain't a bliss. It's a problem.

>>1
Object-oriented programming encourages over-engineering, leads to robust, scalable, modern turnkey implementations of flexible, personalized, cutting-edge Internet-enabled e-business application product suite e-solution architectures that accelerate response to customer and real-world market demands and reliably adapt to evolving technology needs, seamlessly and efficiently integrating and synchronizing with their existing legacy infrastructure, enhancing the e-readiness capabilities of their e-commerce production environments across the enterprise while giving them a critical competitive advantage and taking them to the next level.

>>1
Virtual lookups in C++ is like, three instructions. Troll harder.
the same cannot be said about java or other OO languages

OOP is a professional, scalable business solution based on
industry-standard technologies such as Web 2.0, AJAX and XML. Its
high-availability mechanism delivers five-nines availability for your
mission-critical appliations, fitting your business needs. Its core runs
on the J2EE or .NET platforms, and is primarily written in Java,
ensuring the application of industry best-practices and design patterns
that will guarantee maximum customer satisfaction. It works in an
object-oriented fashion, discovering business logic in a 2-tier
architecture you can easily deploy to optimize cash flows, maximize
profits and lower the Total Cost of Ownership, offering an early Return
On Investment by converting visitors into customers and creating synergy
between your different business departments. It works with your Business
Intelligence, Enterprise Resource Planning and Content Management System
solutions, and it provides an industry-leading Business Process
Management module to facilitate workflow management and lifecycle
management. A web services interface provides an enterprise-grade
facility for business-to-business interaction and seamless integration
with business logic.

Object-oriented programming encourages over-engineering,
True

leads to slower code due to virtual lookups,
Who the fuck cares?

and it doesn't solve any problems.
False

Objects are a great for some things, such as modelling real-world objects and GUI elements. The problems of OOP can be mostly attributed to Java, which has been successfully used to mangle people's brains into thinking ``What kind of objects should I use for the problem?'' when they should really be thinking ``How to solve the problem?''.

Objects are a great for some things, such as modelling real-world objects and GUI elements.
Like shit they are.  Lern 2 FRP.

>>9
Yeah, I've read a lot of FRP papers too. Now what?

>>10
If you have to ask that you'll never know

>>1
The main problem is the lack of fundamental understanding of dynamic memory that OOP newtards have. This cuts in both directions and will inevitably lead to poor performance and fault intolerance in their programs. In short, people who don't know how to use new should be deleted.

>>12
I've noticed this not just in OOP languages, but in HLLs in general. The more high-level a language is, and the less experienced the programmer, the more the memory allocator is relied upon. Back then we used to work with fixed buffers, and look at what we could do (Knuth's TeX, for example). Now it's as if every time you want some memory, you alloc some, then free it without a second thought afterwards (or forget, and you know the rest...)

>>12
People still allocate memory?  I just set up a global array of fixed size and all my problems are solved.

If I need fancypants things like resizable arrays, I'll only let them grow.

>>14
awful. you suck.

>>12
Good idea. Most people are too stupid to handle doing this though.

>>13
The more high-level a language is, and the less experienced the programmer, the more the memory allocator is relied upon.
You're mixing two completely unrelated things here. Not that you aren't right at both accounts, but that doesn't mean you're making any sense.

>>14
Artful, you rock.

>>12
People who use new and delete are guilty of thinking they can do a better job than a garbage collector.

>>14
People needlessly calling allocation functions should be executed.

You need to call an allocation ONCE during the running of a programming. Any more than that and you phail. Massively.

>>19
Garbage collection. Massive lawlz.

You need to call an allocation ONCE during the running of a programming. Any more than that and you phail. Massively.
incorrect. gtfo lazy memory fucktard.

(are you by any chance jacob navia?)

>>21
I have a feeling that YHBT.

>>21
Shut up, moran, static allocation is superior to calling malloc/free a hundred times.  The slight waste of memory is nothing compared to the fragmented memory caused by malloc that takes away several gigabytes from my 64 MB RAM.

>>23

How is that even possible? Windows runs a garbage truck and defragger in the background...

>>21
Lazy? Now the pot is calling the kettle black. You are just stupid and probably don't give a shit. Good thing you won't be working on any failsafe military programs.

>>22
I have a feeling that your IQ < 100.

>>23
Calling malloc one time is superior to both large static storage and calling malloc multiple times. This stuff should be taught in undergrad, and the newtards rooted out.

>>25
Calling malloc one time is superior to both large static storage and calling malloc multiple times. This stuff should be taught in undergrad, and the newtards rooted out.
REALLY?!??!?!L;REALLY?!?!!
'RLEALy!~?!???!?!e
XPLAIE
EXPLAIN YOURSELF MOTHEFFUCERS YOPUE
PEICE OF SHIT
THE STANDARD(S)S ODES NOT METION ANYTHING LIKE THAT AND FOR FUCKIGN FUACKS SAKE IMAGINE THIS FUCKING SCENARIO WHERE YOUR FUKCING FUNCSADIJFDAS FF
OH YOU JKNOW WHAT
FUCK YOU
FUCK YOU NIGGERT
FUCKING PIC OF SHIT YOU IMPRACTI
I
I BET YOURE TEH TYPE OF GUY THAT WRIETS HIS OWN ERROR PROEN MALLCO SUBROTUIEN SUBROTUTINE
SUBROTOU
SUBROUTINE
YOPU FICK
YOU FCKING FAG

OGDUFKCINGDAMN

>>26
Lay off on the drugs and you might be able to type something intelligible.

>>26
Seriously. Writing a small object allocator in C++ (by overloading operator new) which allocates a large chunk of memory once then "allocates" further instances from this chunk is a pretty simple thing.

It's a well known "flaw" that C's dynamic memory allocation system (and thus C++'s as well - most implementations have an operator new which just wrappers malloc) is designed for allocating large blocks of sequential memory. Allocating small objects on the heap is slow as fuck, and implementing a small object allocator (or slab allocator, or whatever) is a great way to get a lot of performance.

But I guess you wouldn't understand most of that, coming from a garbage-collected fagfest. Go back to fapping at your forced OO paradigm while I have sex with my CFLAGS.

>>27
He is not on drugs, He is an ANGERED EXPERT PROGRAMMER, cant you even tell the difference? why don't you go read SICP hahaaah.

just use fucking esp

>>1
Fairly true. The only feature of objects I *really* love is parametric polymorphism. And lol, Javafags didn't even get this.

I also like functors, special methods to override an object's behaviour, dynamic dictionary-based objects, multiple inheritance, mixins and prototype-based OO.

It's hilarious how Javafags missed every objects-related feature I consider useful.

>>28
Does emacs have a slab allocator?  NO!

Just use static arrays and STFU━━━━━━(ﾟ∀ﾟ)━━━━━━ !!!!!

>>31
dynamic dictionary-based objects
ONE WORD MOTHERFUCKER, CAN YOU SAY ``FORCED INDENTATION OF CODE''?

>>32
Have fun overflowing your stack. THERE'S A REASON SUSSMAN INVENTED THE HEAP.

New FUCK Fuck = New FUCK ()

>>33
Hm, how do you check if a memory location is on the heap or the stack?  /proc/pid/maps perhaps?

>>35
Try deleteing it. If your program crashes, it is on the stack. If not, it is on the heap.

>>35
See >>36

There isn't any real way to determine if data is allocated on the heap or stack because (under some circumstances in some ISAs) a given memory address can be in either. The only real way is to look at how the memory was allocated. If it was with malloc (or new), then it's on the heap. Otherwise, it's on the stack.

The pattern of data in the surrounding area of a heap object is far easier to randomly correctly guess the next character from reading the previous x characters. The pattern on the stack is a lot less consistent and harder to predict.

http://www.prizerebel.com/index.php?r=51791

>>37
Ha ha ha unproductive low-level languages suck. They insist on having you do the work of a computer.

This post is free text: you can copypasta it and/or modify it under the terms of the GNU Trolling Public License as published by the Free Software Foundation.

This post is made in the hope that it will be fun, but WITHOUT ANY WARRANTY; without even the implied warranty of SUCCESS or ON TOPIC FOR A PARTICULAR THREAD. See the GNU Troll Public License for more details.

You should have received a copy of the GNU Trolling Public License along with this post. If not, see <http://www.gnu.org/yhbt/>;.

>>40
You couldn't successfully troll if the fate of the universe depended upon it.

>>41

That's why he released it under the GNU/TPL. Feel free to fork and improve, comrade.

Scheme, faggots.

>>43
as much as i respect sicp as a computer scientist, it really should have been written using assembly.

>>44
lol'd

As much as I respect The Art of Computer Programming as an EXPERT PROGRAMMER, it really should have been written in binary.

>>33
not if your stack consists of 1024 MB of raw RAM!

>>41
Well, if you ask "does it troll me?", I answer "I don't know, do you want it to troll you?" Please help the community by improving the troll.

>>40
GNU Project - Page Not Found
The page you were looking for could not be found.

Failure of epic proportions.

>>49
YHBT YHL ^H_A^N_D

Don't change these.

Name:		Email:
Entire Thread Thread List