Macros can be useful but I feel like we should ban certain people from touching them.
For example, imagine if someone were to use the C preprocessor to create an elaborate object orientation system for C, calling it GObject, and then create an entire graphics stack up to and including a desktop environment, called, say, GNOME.
I think that's the kind of person who should no longer be allowed to use the C preprocessor.
I think the most important lesson to learn from free software is that after people have enough money to put food on the table they're willing to put time into something with no monetary benefit
You: Intel architecture
Me: Actually, Intel is the manufacturer. You're thinking of Intel's monster.
Fun prank: `chsh -s /usr/bin/node`
glitched: Internet Of The Thing
tired: Internet of Things
wired: Internet of Being Kind to Each Other
The developers of the macro had this to say:
"We are very sorry that this has happened and are working hard to clean it up. In the meantime, do not panic. The macro is hygienic and will not harm the local environment."
Breaking: a lisp macro has broken free from its interpreter and expanded to half the size of Nebraska
Kernel: ok, ok, it’s just a null pointer, no reason to panic
Kernel: (internally) AAAAAAAAAAA
Gopher over HTTP
Base 64? You mean hexacontatetrimal numbers?
please remember the more swords you have the more valid you are