3 ms·
It seems to me that limiting possibilities is the best way to reduce complexity. Immutability, strong types, no goto, no global state and the list goes on. The
by xupybd 5y ago
It seems to me that limiting possibilities is the best way to reduce complexity.
Immutability, strong types, no goto, no global state and the list goes on. These all avoid the complexity of too many possibilities.
- dgb23 5y agoAll of those limitations can add complexity, specifically when they are not a good fit and you need to either work around them or break their rules. There are plenty of examples where immutability is not the right fit (or even possible) or when static types are not helpful but just increase verbosity (and complexity). They might be good defaults (especially immutability if you can afford it) but not strictly the best way to reduce complexity in every circumstance.
- mikewarot 5y agoAll programs have a global state. Forcing that state onto the stack doesn't always make things simpler.