Honestly, I'm not for or against skins one way or another - I see the value and the potential pitfalls as described by various folks. What is more interesting from this thread is the potential ability of Nim to allow developing such skins in so called user-space. If I could write a completely alternate syntax without having change the compiler code, that means I have that much more power and expressiveness that can be used to solve other real world problems.
We already have templates and macros and other fun features that make Nim extremely capable and attractive. If Nim were capable of skins as a language, not as a goal in and of itself but as a consequence of an expanded feature set, it would only make it more attractive, not less. If someone wanted to create an alternate or extended syntax just to get rid of white-space, that's not really solving anything material but that's their call. If they come up with some brilliant alternate syntax that many people subscribe to, so be it, let them be empowered. Coffeescript didn't break Javascript, it created an alternate happy community thanks to Javascript's expressiveness and that's the real value. Ultimately, such power will be used to solve difficult problems much more often than splintering the Nim community with a hundred bogus skins.
