I still think it's a far superior way to introduce newbies to Scheme than emacs, but it's definitely flawed.
If you are really resource constrained it's easy to go to the settings and restrict memory use, and turn off tools you don't intend to use. If you have a really slow machine there is even a minimal DrRacket.
Bloat is a content-less word for software.
Most naive users complain about "bloat" for stuff like program file sizes on disk, not knowing that most of it is assets (icons, etc).
Others think that having two many options in the menus, features etc slow the program down, not realizing that in most programs stuff is run and loaded dynamically, and a features you don't use don't affect the speed at all.
Others yet think that only 20% of the features is needed (those that THEY use, of course) ignoring the fact that while a core set of features is common to all users, a large part of them are in non-overlapping set. E.g.: "Who needs a word-counter in Word?" -- well, if you're a journalist, it's your #1 more useful function.
[Disclaimer: I also like the idea of RSR7S small.]
Just now there is a major reorganization in the Racket repository. The idea is to split it in a core part and may small packages. The objective is one day having many installers. For example one with only the minimal support for racket, one with everything including the kitchen sink, ...
My most powerful personal computer being a laptop with an 1.8GHz i5, and 4GB of ram. Yeah, that's very modest by 2014 standards, but I really think that it should be able to handle DrRacket better than it does. As it is, it is just too slow for me to put up with. I think that something that at least somewhat targets the education niche should be able to perform well on old hardware (the type of machine you might typically find in a university computer lab).
1) Turn off the background syntax checker (click the dot in the bottom right corner).
2) Turn off "Program contour" in the "View menu" if you happen to have it on.
If that's not enough:
3) Use "Limit Memory" in the "Racket" menu to limit the memory use for the user program to say 256MB.
4) For more speed: In the language menu use "Choose language...", click the "Show details" button and turn ofd debugging. (But that's a last resort)