Den man. 7. jan. 2019 kl. 01.45 skrev Paulo Matos <pmatos@linki.tools>: > I don't really understand the risky bet comment. What's a risky bet? To > use Racket on RISC-V for production? Well, yes, it doesn't run yet. > RacketCS doesn't compile because the RISC-V backend for Chez is not > finished, Racket doesn't compile because libffi, at least, hasn't been > ported to RISC-V.
The presence of a Debian package had made me think that Racket indeed compiled and ran on that architecture - I suppose I must have misunderstood. "Production" means very different things for different contexts, and I'm in one where it would be fine to have something that was a bit experimental but not where I can write a thing on my laptop and then find out that I can't run it at all when it comes time to use it on a RISC-V box in a few weeks. Thanks for helping me understand the current state of things! > However, it's not a risky bet to support the porting of Racket for > RISC-V because both are really mature projects which are here to stay > and lots can be done on RISC-V since the base ISA's and some extension > specs have been frozen. Totally agree - I think there's a bright future for RISC-V. I was just hoping to be able to write a little prototype in Racket and run it in a couple weeks, but it seems that I should probably wait a year or so before I start doing that, and write the little prototype in something else. Thanks for the info! Thanks again for taking the time. David -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
