On Mon, May 20, 2013 at 10:04 PM, Neil Van Dyke <n...@neilvandyke.org> wrote: > [snip] > > Example: Imagine I'm in the middle of writing a Racket program and am > wondering about characteristics of some kind of I/O port in Racket. With > transparent source accessibility, I can just click on an identifier in my > program in DrRacket to start browsing the implementation. Maybe I see a > possible improvement, or seeing the source pre-empts yet another email list > question that otherwise only Matthew could answer, or I feel empowered to go > add a new feature. If the source is not as accessible, then I'm more likely > to be a mere naive user of the tools, rather than to understand the tools > and help improve them. >
+inf.0 Though the easiest way to make the source available is just to keep it in the distribution. I'll be sad to see it go. -Jon _________________________ Racket Developers list: http://lists.racket-lang.org/dev
