What is the best programming paradigm for managing large codebases?
>>54435049
object oriented
meta programming sounds cool
>>54436479
Lisp?
>>54436502
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)
>>54435049
Not letting the original coders quit.
>>54436609
lol good luck
>>54436539
macro that kind of shit
functional
>>54440357
Haskell?
>>54436540
this
>>54435049
Kidnapping Linus Torvalds and making him do it.
>>54435049
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
>>54442838
Who are you quoting?
>>54442880
noone, just a statement
>>54435049
>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.
>>54442907
Gotta get that meme game up, senpai
>>54435049
functional because referential transparency and modularity through function composition
>>54438496
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.
>>54436609
>coders
You mean appers surely?
>>54440357
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.