What is the best programming paradigm for managing large codebases?

What is the best programming paradigm for managing large codebases?

object oriented

meta programming sounds cool

Lisp?

I said the name sounds cool but I don't know what it means.

you've pretty much named the exact use case for which object-oriented programming was designed/optimised

interfaces/inheritance, codefile separation and pass-by-reference make it easy to work separately on disparate components/libraries and support modern test/deploy frameworks (plus TDD)

Not letting the original coders quit.

lol good luck

macro that kind of shit

functional

Haskell?

this

Kidnapping Linus Torvalds and making him do it.

can someone write examples of each? i was just learning basic shit when i was in school but always hated oop

the hell is aspect oriented programming?

>Procedural masterrace
its the best
prove me wrong
>protip: you cant

Who are you quoting?

noone, just a statement

>Concurrent is a separate paradigm rather than a program attribute
>Meta-programming is a separate paradigm rather than a language feature
>Imperative is contrasted against Functional (instead of e.g. Declarative)
Whoever made this stupid graph knows more about graphics design than programming languages.

Gotta get that meme game up, senpai

functional because referential transparency and modularity through function composition

Chain them up in the janitor's closet. No-one has to know.

Managing large projects and code bases is why OOP was designed.


It's also why there is such a focus on OOP.

>coders

You mean appers surely?

Literally the worst paradigm for maintaining large codebases.
The worst for working in groups too.

It's great at everything else,
but by that point no one cares.