Re:Racket: Lisp for Learning
by AlexeyBrin on Thursday August 08, 2019 @10:26AM
(#20644872)
Given the Racket2 possible massive syntax changes it seems that using JavaScript was a better choice for a commercial project. That being said I very much prefer Racket to JavaScript for personal/hobby projects.
[ Parent
| on HN ]
Re:Racket: Lisp for Learning
by JoelMcCracken on Thursday August 08, 2019 @11:40AM
(#20645527)
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.
Re:Racket: Lisp for Learning
by traderjane on Thursday August 08, 2019 @11:46AM
(#20645571)
But where will the culture of Racket go? How will the educational texts, documentation, and general conversations go?
Re:Racket: Lisp for Learning
by JoelMcCracken on Thursday August 08, 2019 @12:00PM
(#20645705)
Why 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?
The name "racket2" is too strong.
I suppose because that's a niche dialect, an experiment if you will, not the anointed successor.
They could do an Elixir style fork instead? Although a pure syntax change isn’t as significant as what Elixir changed.
I think it would have been fine based on https://groups.google.com/forum/m/#!msg/racket-users/HiC7z3A...
> No matter how Racket evolves, the community is committed
> to preserving what we have achieved: today's `#lang racket`
> programs will run in the future, and today's
> `#lang racket` modules can be used in future Racket programs.
Yeah. But Racket seems so much cooler.
Re:Racket: Lisp for Learning
by AlexeyBrin on Thursday August 08, 2019 @10:39AM
(#20644999)
Racket really is a nice language, we'll see if/how the situation changes once the Racket2 situation is clarified.