2 ms·
Yes, but I think the other point is well-made, as well: languages that allow this can be very difficult to work in if you have to maintain a large app with mul
by emodendroket 9y ago
Yes, but I think the other point is well-made, as well: languages that allow this can be very difficult to work in if you have to maintain a large app with multiple contributors over a long period of time.
- heretoo 9y agoThe same can be said for function calls, with the indirection they create hiding details of broken and side-effecting implementations. None the less, the opposite is also true. Languages that have macro facilities can aid in writing more legible code. (See `threading` in clojure), or the `loop` macro and regular expression macros in common lisp.
- Roboprog 9y agoWell said. Rambling Java code with little to no abstraction is its own kind of nightmare. Some people are just terrified of any new abstractions, I guess, preferring to work with an endless series of tally marks, rather than these obfuscating “multiplication” and “exponent” complications (exaggerating to make a point - abstract != unintelligible).
- emodendroket 9y agoI think there is probably some middle ground between "no abstraction at all" and "literally anything goes."
- Roboprog 9y agoLCD? Alas, that tends to be the steady state for Enterprise development :-( (I know that’s not literally what you said, but that’s where that “middle ground” attitude leads to: the bottom)