3 ms·
PG has other essays where he claims it's because the lisp version of operators can just do more things. And that's true, lisp macros are way more powerful than
by marcosdumay 3y ago
PG has other essays where he claims it's because the lisp version of operators can just do more things.
And that's true, lisp macros are way more powerful than what most languages support. The newer ones (and some "progressive" old ones) got template systems that are almost as powerful, but the most used languages simply don't have anything comparable.
That said, nowadays using a lot of that kind of feature is normally frowned upon.
- leetrout 3y agoI have a theory it is frowned upon because there are not a lot of small shops left. Everyone wants be a cog at a big tech co where its leetcode interviews and code that large groups can (somewhat) easily maintain. In these cases the languages used are generally uniform so your skills easily transfer and you aren't suffering as many 200% problems by learning both the language and the authors peculiar add-ons. Of course it still happens just not as easy with rigid languages such as Go. It's all tradeoffs.
- marcosdumay 3y agoAs a rule, when something starts deserving being called by "shop", it is already too large for heavy usage of macros. In fact, I'm not sure it scales for more than a single developer. That is, unless you treat them as another language, with tooling, documentation, and stability. Then they scale again, but it requires quite a lot of work.
- leetrout 3y agoIs this website an example? Dang has been talking about a set of performance changes for a long time and I always wonder if it is slow because it is so bespoke.