The main problem with Racket

The main problem with Racket's macro system (and with other syntax-case systems) is that instead of raw s-expressions you're dealing with syntax objects. This becomes very ugly when identifiers are handled: instead of dealing with plain symbols, you're dealing with these syntax values (called “identifiers” in this case) that are essentially a symbol and some opaque information that represents the lexical scope for its source. In several syntax-case systems this is the only difference from defmacro macros, but in the Racket case this applies to everything — identifiers, numbers, other immediate constants, and even function applications, etc — they are all wrapped with additional information.

I try to pop in to this forum from time to time and see if there are any newbie questions I can answer or maybe pick-up a few new tricks. Today marks the longest period of time I have seen between perl posts here --- complete month! I would say that perl is dying. It is still useful to know, but it won't be many people's first choice.