On 6/11/2011 6:30 PM, C. Scott Ananian wrote:
On Sat, Jun 11, 2011 at 1:40 AM, BGB<cr88...@gmail.com> wrote:
"The responsiveness of exploratory programming environments (such as the
Smalltalk programming environment) allows the programmer to concentrate on
the task at hand rather than being distracted by long pauses caused by
compilation or linking."
this is also partly where dynamic script loading and eval can be nifty...
say, one is using an app, and then in the console they type in a command,
say:
;load("scripts/myscript.bs");
and can quickly edit the file, hit the uparrow in the console to re-enter
the prior command, and observe the results.
or, the ability to directly type script commands into the console to observe
results, ...
You should spend some time playing around with the Web Inspector in
Chrome or other Webkit browser. Console, live code editing, lots of
other good stuff. The only big drawback is the complexity of the
system: HTML+CSS+JS is quite a hairy beast.
yeah...
my current strategy already involves some amount of typing commands into
the console...
as noted in the other post, the main role that "load(...)" serves, is
that I am limited to about 100 characters at a time I can type into the
console, which is a limitation.
edit/reload/go is more of a compromise...
but, I was also left recently thinking some about the possible "strangeness"
of me basically creating a vaguely Lisp-like programming environment within
C.
http://en.wikipedia.org/wiki/Greenspun's_Tenth_Rule
--scott
except, in my case, there is a more direct reason:
long ago, I had messed around with Scheme, and implemented a Scheme VM;
many Scheme-like facilities and practices have managed to somewhat
outlive the original VM, but were just sort of kludged back onto C, and
became a part of the baseline coding practice.
or such...
_______________________________________________
fonc mailing list
fonc@vpri.org
http://vpri.org/mailman/listinfo/fonc
