5 ms·

I think my language of focus in 2017 will be Racket. It seems to be the perfect combination of optional (but somewhat static!) strong typing, highly advanced fe

• throwaway7645 10y ago
  I have a comment on Racket below. I like the concept, but it seems to be pretty slow. I'm also not sure how many mini-languages are out there. What the "Red" language team is doing seems to be a similar concept. That makes sense as Racket is a Lisp and Red is mostly from Rebol, but has a native code compiler and comes with a tiny .exe. Their GUI engine is phenomenal.
  • capnrefsmmat 10y ago
    On Scheme benchmarks, Racket does fairly competitively, probably due to its JIT: http://ecraven.github.io/r7rs-benchmarks/benchmark.html http://ecraven.github.io/r7rs-benchmarks/benchmark.html (Chez is still freakishly fast.) However, if you're writing code in DrRacket, it has full debugging information enabled, which may slow the code down. So your REPL performance in DrRacket may be slower than if you ran Racket from the command line. https://docs.racket-lang.org/guide/performance.html https://docs.racket-lang.org/guide/performance.html
    • royallthefourth 10y ago
      The debugging slows the code down a ton in my experience, and it also prevents futures from running in parallel. Trying out the futures code from the guide, failing to disable debugging slows down the final Mandelbrot example by something like 100x on my machine. Fortunately, DrRacket's friendly GUI makes it pretty easy to toggle debugging. I leave it in place most of the time, but occasionally the slowdown is just unbearable.
      • throwaway7645 10y ago
        Thanks for the tips! I'd like to use ChezScheme, but haven't found a good way to get into it.