With the improvements in the upcoming v7.8 release, Racket CS provides all of the functionality of Racket BC (the current default implementation). Also, end-to-end performance measurements increasingly favor Racket CS. For example, Racket CS now builds a distribution slightly faster and in slightly less memory than Racket BC:
https://build-plot.racket-lang.org/ https://build-plot-cs.racket-lang.org/ It's time to consider shifting the Racket release to use Racket CS as the default --- while Racket BC will remain an option for a long time to come. We (the release managers) propose the following rule to trigger the switch to Racket CS in the default distribution: Between this release and the next, if Racket CS testing and use uncover no bugs that are more serious than ones typically discovered for Racket BC, then Racket CS becomes the default for the next release. At the earliest, the switch would happen with the release *after* the soon-to-be-released v7.8. Our expectation is that the switch would happen with the next release (in October), but we'll see how that expectation lines up with reality. This rule is somewhat subjective, in that "more serious" and "typical" are in the eye of the beholder, but we keep a close eye on the results of the pkg-build service as well as Racket tests. We'll also count performance problems as bugs, so Racket CS must not have substantial known performance problems relative to Racket BC. Jay, John, Matthew, Matthias, Robby, Ryan, Sam, and Vincent (the release managers) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/20200730064636.29e%40sirmail.smtp.cs.utah.edu.
