True that infix < doesn't appear right after parens, but in the minds of most people, there isn't really a notion of "infix" as an entity unto itself. The alligator just eats the bigger fish.
Really, the problem is that a small amount of whitespace can change the meaning of the code.
(< 1 2) => #t
(<1 2) => #f
...for a convenience function <1 that semantically means "is less than 1". Maybe you wouldn't define such a function, but having to think about it at all or having to mentally redefine < somewhat validates the idea that the syntax here is a stumbling point.
Comments
True that infix < doesn't appear right after parens, but in the minds of most people, there isn't really a notion of "infix" as an entity unto itself. The alligator just eats the bigger fish.
Really, the problem is that a small amount of whitespace can change the meaning of the code.
(< 1 2) => #t
(<1 2) => #f
...for a convenience function <1 that semantically means "is less than 1". Maybe you wouldn't define such a function, but having to think about it at all or having to mentally redefine < somewhat validates the idea that the syntax here is a stumbling point.
I do remember stumbling on < early on, but now I don't get it wrong any more often than I do with infix.