I can tell you why: it encourages the programmer to

Question

I can tell you why: it encourages the programmer to

organize their code into units (objects) that sound nifty but are usually not descriptive, or even that well related, to the work the computer actually needs to do and in that way serve as a distraction from that actual work and the understanding of it.

How bad is that? Well, it's not like you can't program like that but it's pretty lame. It's like reading a book with the author telling you how he's feeling while he's writing it or whether he needed to scratch his ass at the time all over the place. It's just better without it.

Also OOP just doesn't deliver on it's promises. I think newbies feel like the objects represent good modules that are flexible and provide good benefits to the programmer but good modularity is only as good as a module can represent something real and objects are nearly always a poor representation of the reality they claim to be.

There's more reasons than that but that's enough for a start

0

18.09.2024

6 ответов

13 просмотров

Chiyando Автор вопроса

. .
So how do you program, do you use a particular par...

That's a big question. I'll write up a longish answer for you over some time

0

3 месяца назад

QWxp

. .
So how do you program, do you use a particular par...

Стикер

0

3 месяца назад

Chiyando Автор вопроса

. .
So how do you program, do you use a particular par...

I probably won't get back to you actually. It takes too long. But let's just say this: I like type checking. I like pure functions. I like unit tests. I like designing around the actual data that's needed. I like assertions (design by contract). I like actually creating designs of the software before I start coding. I like building prototypes for testing uncertain things

0

3 месяца назад

D

. .
So how do you program, do you use a particular par...

Declarative paradigm

0

3 месяца назад

. .

D
Declarative paradigm

prolog?, god

0

3 месяца назад