Racket: Lisp for Learning

#1

Post by chmaynard » Thu, Aug 08, 2019, 12:55 PM UTC

Re: Racket: Lisp for Learning

#2

Post by jimbob45 » Thu, Aug 08, 2019, 2:11 PM UTC

Carmack is a huge fan of Racket. He was going to use it as the scripting language for VR until the Oculus execs made him use JavaScript instead (boooooo)

https://twitter.com/id_aa_carmack/status/807797812700348416

Re: Racket: Lisp for Learning

#3

Post by 6thaccount2 » Thu, Aug 08, 2019, 2:17 PM UTC

jimbob45 wrote: post #2

Carmack is a huge fan of Racket. He was going to use it as the scripting language for VR until the Oculus execs made him use JavaScript instead (boooooo) https://twitter.com/id_aa_carmack/status/807797812700348416

I think I heard that even his wife didn't want him to teach their son Racket and wanted him to learn Java. Not sure if true.

Re: Racket: Lisp for Learning

#4

Post by AlexeyBrin » Thu, Aug 08, 2019, 2:26 PM UTC

jimbob45 wrote: post #2

Carmack is a huge fan of Racket. He was going to use it as the scripting language for VR until the Oculus execs made him use JavaScript instead (boooooo) https://twitter.com/id_aa_carmack/status/807797812700348416

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.

Re: Racket: Lisp for Learning

#5

Post by AlexeyBrin » Thu, Aug 08, 2019, 2:31 PM UTC

I really like Racket, but the potential breaking massive syntax change in Racket2 makes me really uncomfortable in using or recommending Racket to other people, at least until the situation is clarified.

Re: Racket: Lisp for Learning

#6

Post by aswanson » Thu, Aug 08, 2019, 2:34 PM UTC

AlexeyBrin wrote: post #4

jimbob45 wrote: post #2

Carmack is a huge fan of Racket. He was going to use it as the scripting language for VR until the Oculus execs made him use JavaScript instead (boooooo) https://twitter.com/id_aa_carmack/status/807797812700348416

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.

Yeah. But Racket seems so much cooler.

Re: Racket: Lisp for Learning

#7

Post by gekkonier » Thu, Aug 08, 2019, 2:37 PM UTC

AlexeyBrin wrote: post #5

I really like Racket, but the potential breaking massive syntax change in Racket2 makes me really uncomfortable in using or recommending Racket to other people, at least until the situation is clarified.

#lang racket is here to stay parallel to #lang racket2

Racket is a lot of languages, not only one. You can mix in Racket as you like. You can mix #lang racket and #lang typed/racket with #lang datalog in one application if you like. With racket2 those options will not fade away I guess.

Re: Racket: Lisp for Learning

#8

Post by AlexeyBrin » Thu, Aug 08, 2019, 2:39 PM UTC

aswanson wrote: post #6

AlexeyBrin wrote: post #4

Earlier quoted context omitted.

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.

Yeah. But Racket seems so much cooler.

Racket really is a nice language, we'll see if/how the situation changes once the Racket2 situation is clarified.

Re: Racket: Lisp for Learning

#9

Post by tombert » Thu, Aug 08, 2019, 2:46 PM UTC

Does Racket support "real" multithreading yet? I remember looking at their documentation a few years ago and it only had support for a green-threading thing, which (along with the first-class hashmaps) steered me towards Clojure.

Re: Racket: Lisp for Learning

#10

Post by wtetzner » Thu, Aug 08, 2019, 2:49 PM UTC

AlexeyBrin wrote: post #4

jimbob45 wrote: post #2

Carmack is a huge fan of Racket. He was going to use it as the scripting language for VR until the Oculus execs made him use JavaScript instead (boooooo) https://twitter.com/id_aa_carmack/status/807797812700348416

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.

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.