3 ms·
Very good point — that's why good abstractions are such a win. With functions, I don't need to think about all the code needed to read the body of an HTTP requ
by wtbob 10y ago
Very good point — that's why good abstractions are such a win. With functions, I don't need to think about all the code needed to read the body of an HTTP request; I just read it.
That's also why I think that macros are so valuable: a single macro can abstract away an extremely complex and tricky piece of code into a single line, or two.
With the right abstractions, we can turn 10^6 projects back into 10^3 projects.
- ludamad 10y agoThis alludes to another issue: you can pack a lot into one line, but that doesn't necessarily mean it'll be a tractable line of code lest something goes wrong
- wtbob 10y agoTrue enough, and it applies to functions as well as macros. A function named getThingList which also sets the user's password and send a rude email to the Premier of Elbonia is just as bad as an unhygienic macro!
- deleted 10y ago[deleted]