2 ms·
> I'd start with deemphasizing Dr. Racket. Sure it's great and all, but most people aren't gonna use special IDE for your language. I suspect the first impress
by neilv 7y ago
> I'd start with deemphasizing Dr. Racket. Sure it's great and all, but most people aren't gonna use special IDE for your language.
I suspect the first impression of DrRacket has been scaring off real developers since the start (as it initially did to me, ~18 years ago).
DrRacket was designed for students with no programming experience at all (and then some nice pro features were added atop that).
Put DrRacket first thing in HtDP, but be very careful about first impressions elsewhere. (And this doesn't mean adding an additional explanatory paragraph, or an additional manual about all your IDE/editor options. Racket already has a massive wall of documentation manuals, with the useful stuff scattered all over. People tend to not read stuff on the Web under even the best of conditions.)