I think the smalltalk approach failed on the merits. I don't want it today personally.
-
-
You don't want what part of it? An image-based environment? I can agree with that. Immediate and rich feedback OTOH...
1 reply 0 retweets 1 like -
Replying to @robotlolita @stilkov and
Immediate feedback is great. But can be done without source stored in an image.
3 replies 0 retweets 1 like -
I think we disagree on Smalltalk's strengths being the use of an image-based format to store programs, then.
1 reply 0 retweets 0 likes -
Replying to @robotlolita @wycats and
To me Smalltalk's strengths are much more in the language's semantics and integrated set of reflective tooling w/ immediate feedback.
3 replies 0 retweets 1 like -
Replying to @robotlolita @stilkov and
I'm a fan of those. Ruby has a good amount of the language level semantics. Someone should build a class browser for ruby!
2 replies 0 retweets 1 like -
IMHO lexical scoping at the top level isn't very compatible with the kind of editors Smalltalk had.
1 reply 0 retweets 0 likes -
-
Replying to @wycats @robotlolita and
"integrated set of reflective tooling with immediate feedback" doesn't seem to depend on this very much?
2 replies 0 retweets 0 likes -
Unless your scope is first-class and names there late-bound, you can't change it without VM hacks (e.g.: what Chrome debugger does)
2 replies 0 retweets 0 likes
Ruby `binding` and hacks like Binding.of_caller get you there.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.