2 ms·
I always thought different paradigms suited different problem domains rather than different people. I'm not a software engineer by trade, but just for example,
by ldp01 10y ago
I always thought different paradigms suited different problem domains rather than different people.
I'm not a software engineer by trade, but just for example, I've recently been mucking around making my own videogames and the object-oriented paradigm using the components pattern seems like a very natural way to conceptualise a videogame. E.g. Objects in the game (NPCs, environment) start as a basic object and are given specific behaviours by adding components.
Alternatively, I sometimes have to write R code for data analysis and in that case the style of using pipe operators to chain lots of functions together is perfect for readability and for reasoning about the code.
- TuringTest 10y ago> I always thought different paradigms suited different problem domains rather than different people. This. Any imperative program can be formally encoded as an immutable functional program, and vice-versa. Therefore, which paradigm to choose is a matter of what style fits the problem at hand better, and how comfortable you are with the paradigm. But this is true of any coding convention.