@samth: I’ll add more about compiler times in the extended version (which I imagine posting at one of the above URLs, while the short version is on the Racket blog). I had lost track of the cost of schemify, and that’s worth drawing out even in the short version. Did you have in mind something specific for a high-level takeaway? I intentionally refrained from drawing further conclusions from the summary facts in the last paragraph of the introduction, because I don’t know the conclusions. I’ll add a second and more explicit pointer to the racket7 repo at the end. Requests for help don’t seem to work in this phase, so I’ll skip that.

Upon further reflection, I think that paragraph is enough in the intro. I think we should add some more instructions at the top of the racket7 repo for building and running the cs version, since people will want to try and currently it’s several pointers to follow to get to the actual instructions.

Also, what’s the command you ran to get the “Racket” startup time column (I’m never sure what the best way to measure that is)

time racket -n

posted

@mflatt do you plan to post to one or both lists? I expect that many people don’t read the blog who do subscribe.

It’s hard to know which communication channels to use, and there doesn’t seem to be a precedent for posting blog alerts on the mailing list. But I guess it makes sense to post to the dev list, since the previous Racket-on-Chez messages went there.