4 ms·
Very much an overreaction. The whole point of Racket is to support multiple syntaxes. The idea that a future Racket would NOT support the current syntax seems a
by JoelMcCracken 7y ago
Very much an overreaction. The whole point of Racket is to support multiple syntaxes. The idea that a future Racket would NOT support the current syntax seems absurd.
But really there are lots of other, better reasons to use JS over Racket for a major commercial project, which may or may not be actually a good call, but a new proposed syntax is not one of them.
- traderjane 7y agoBut where will the culture of Racket go? How will the educational texts, documentation, and general conversations go?
- dmix 7y agoThey could do an Elixir style fork instead? Although a pure syntax change isn’t as significant as what Elixir changed.
- JoelMcCracken 7y agoWhy does the same conversation not come up when discussing typed racket? Is the introduction of a static type system really less culture-shaking than surface syntax?