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.

>>23
Then what about the zoo of:
(syntax-e stx) (syntax->datum stx) (syntax->list stx) (syntax-property #'[foo] 'paren-shape) (quote-syntax when) (datum->syntax context-stx input-sexpr) (syntax-rules () ...) (raise-syntax-error ...) (syntax-parameterize ...)  (require (lib "stxparam.ss" "mzlib")) (make-rename-transformer ...) (define-syntax-parameter ..) (syntax-source stx) (syntax-case stx) (define-syntax (while stx) ...) (with-syntax ...) (syntax-position stx) (syntax-line stx) (syntax-column stx)