4 ms·

> Internally, Racket's intermediate compatibility layer over operating-system facilities has been moved into its own library, "rktio", so it can be used in futu

> Internally, Racket's intermediate compatibility layer over operating-system facilities has been moved into its own library, "rktio", so it can be used in future Racket implementations. Presumably by "future racket implementations" they mean the Racket 7 move to Chez Scheme: https://news.ycombinator.com/item?id=13656397 https://news.ycombinator.com/item?id=13656397 Also, this seems like a neat thing for people needing to deploy racket code x-platform: > Racket supports cross-compilation of executables in more cases, including executables that depend on packages for foreign libraries.

dragonwriter 9y ago
> Presumably by "future racket implementations" they mean the Racket 7 move to Chez Scheme: Presumably, it's broader than that, and applies to any new VMs enabled by the Racket-in-Racket effort, not just the expected move to Chez as the primary VM.
- peatmoss 9y ago
  Good point. I've wondered if the "write more of Racket in Racket" effort required by the move to Chez Scheme will result in an easier path to Racketscript. IIRC, Clojurescript was helped along by something similar.
- metaobject 9y ago
  Is anyone aware of any languages targeting the Racket VM? Any thoughts on whether the Racket VM would be a more pleasant VM target than, say, the JVM or the .Net CLR?
  - peatmoss 9y ago
    The VM itself without the "racket is a language for building languages" thing? Not that I know of. That being said, Racket has a LOT of languages built on it. For example, this site (Hacker News) is built in Arc, which is built on an old version of Racket. EDIT: Also worth noting that Racket will move to an even more performant runtime (Chez Scheme) at some point in the future.
  - notjack 9y ago
    The "Racket VM" is designed from the ground up for other languages to be built on top of it (hence the #lang line at the beginning of every file) so it would likely be much better. Hackett[1] is a Haskell-like lang built on top of racket, for a nontrivial example. [1] https://github.com/lexi-lambda/hackett https://github.com/lexi-lambda/hackett

dragonwriter 9y ago

> Presumably by "future racket implementations" they mean the Racket 7 move to Chez Scheme: Presumably, it's broader than that, and applies to any new VMs enabled by the Racket-in-Racket effort, not just the expected move to Chez as the primary VM.

peatmoss 9y ago
Good point. I've wondered if the "write more of Racket in Racket" effort required by the move to Chez Scheme will result in an easier path to Racketscript. IIRC, Clojurescript was helped along by something similar.
metaobject 9y ago
Is anyone aware of any languages targeting the Racket VM? Any thoughts on whether the Racket VM would be a more pleasant VM target than, say, the JVM or the .Net CLR?
- peatmoss 9y ago
  The VM itself without the "racket is a language for building languages" thing? Not that I know of. That being said, Racket has a LOT of languages built on it. For example, this site (Hacker News) is built in Arc, which is built on an old version of Racket. EDIT: Also worth noting that Racket will move to an even more performant runtime (Chez Scheme) at some point in the future.
- notjack 9y ago
  The "Racket VM" is designed from the ground up for other languages to be built on top of it (hence the #lang line at the beginning of every file) so it would likely be much better. Hackett[1] is a Haskell-like lang built on top of racket, for a nontrivial example. [1] https://github.com/lexi-lambda/hackett https://github.com/lexi-lambda/hackett