Yeah, Rust’s macro system feels like a double-edged sword — amazing power, but with a big learning curve. The tooling and syntax definitely make simple meta-programming harder than it should be.
So basically, macros are like dark magic — everyone warns you not to use them, but half the ecosystem runs on them anyway
True, macros in Rust can feel heavy, but they also enable some powerful abstractions you just can’t get otherwise. I guess the “don’t write macros” advice is more about avoiding overuse than rejecting them completely.
Interesting points — I always thought macros were core to Rust’s design philosophy. Do you think procedural macros will ever get simpler, or is the complexity kind of intentional for safety?
<!doctype html> <html> <body> <style> body { padding: 50px; } span { display: inline-block; background: #a0ffa0; padding: 20px; } </style> <span> Edit the page on top, see the result on the bottom. </span> </body>…
Yeah, Rust’s macro system feels like a double-edged sword — amazing power, but with a big learning curve. The tooling and syntax definitely make simple meta-programming harder than it should be.
So basically, macros are like dark magic — everyone warns you not to use them, but half the ecosystem runs on them anyway
True, macros in Rust can feel heavy, but they also enable some powerful abstractions you just can’t get otherwise. I guess the “don’t write macros” advice is more about avoiding overuse than rejecting them completely.
Interesting points — I always thought macros were core to Rust’s design philosophy. Do you think procedural macros will ever get simpler, or is the complexity kind of intentional for safety?
<!doctype html> <html> <body> <style> body { padding: 50px; } span { display: inline-block; background: #a0ffa0; padding: 20px; } </style> <span> Edit the page on top, see the result on the bottom. </span> </body>…