Re:From design patterns to category theory
by 201709User on Thursday October 05, 2017 @06:30AM
(#15408032)
It's better to have 50 keywords than 1000 nested brackets.
[ Parent
| on HN ]
Re:From design patterns to category theory
by empthought on Thursday October 05, 2017 @07:04AM
(#15408196)
Personally I don't see the advantage of )}]]})} over ))))))).
Re:From design patterns to category theory
by kazinator on Thursday October 05, 2017 @04:09PM
(#15412213)
It's more time consuming to close )}]]})}. With ))) we just repeatedly type ))) until the cursor jumps to the target opening paren we are trying to close. With a mixture of different parens we have to interrupt what we are doing and determine the correct parens which will continue the closing sequence.
Re:From design patterns to category theory
by flavio81 on Friday October 06, 2017 @01:38PM
(#15418645)
>With ))) we just repeatedly type ))) until the cursor jumps to the target opening paren we are trying to close.
Exactly.
Or, the IDE can close all the parens for you: SLIME command "slime-close-all-parens-in-sexp", which you can map to whatever key combination you want.
Re:From design patterns to category theory
by Udik on Thursday October 05, 2017 @08:05AM
(#15408430)
I think there are people who value completeness- they enjoy working on systems with many rules tailored for specific use cases, and like accumulating knowledge about which rule is the correct one to apply in each situation; and there are people who value open-endedness- systems that have few simple rules that can be combined to obtain novel and unexpected results, even if these are not as optimized as they could be in a more complete system.
I picture the difference as that between a role playing game and chess: complex, domain-specific rules on one side, simple and abstract rules on the other.