r/programming • • May 28 '14

"Compression-oriented programming" - Casey Muratori's blog

http://mollyrocket.com/casey/stream_0019.html
125 Upvotes

67 comments sorted by

View all comments

5

u/archagon May 28 '14 edited May 28 '14

I wish I could read this article with a clear mind, but the author's stance is just so... bloody arrogant that I have a hard time doing it. How can you say that object orientation is "objectively bad" when most of the best software in the world is written using object-oriented principles? I dunno — maybe the decades of research starting all the way from Smalltalk have actually been conducted by very intelligent computer scientists who knew what they were talking about? In my experience, it seems that it's mostly old-school programmers in their 40s who prefer the described imperative approach. Given the absolute cornucopia of fascinating new programming paradigms out there today, I feel that they're a bit stuck in the past.

Additionally, I know of literally zero programmers who write things out on index cards and create rigid Employee/Manager/Contractor-like hierarchies.

(With that said, enough smart people have complained about OO that I'm willing to give it more thought.)

-1

u/BadgerSong May 28 '14

I have to say I agree I mean he takes OOP to the extreme while anyone who's had the misfortune to work on code that's heavily 'compressed' to the extreme could say the same. I mean who doesn't love going though n levels of abstractions to find out what a function actually does.

2

u/loup-vaillant Jun 01 '14

Properly compressed code doesn't have many layers of abstractions. Each layer means more code, so they really have to pay off. Too many layers doesn't mean less code, it means more.

If you want to compress your code to the extreme, you would use few layers of abstractions, and maximize their power instead. For instance, you could implement and use an external DSL. It's just one layer, but a potentially very powerful one.