It's quite sad that Smalltalk-style envs didn't win and we were left with editing text files in text editors instead :(
-
-
Replying to @robotlolita @awbjs and
This continues to drive me crazy. The file-based approach won because it’s *better*. You can’t compete with the existing tooling for files.
4 replies 0 retweets 2 likes -
Replying to @stilkov @robotlolita and
Indeed. "everything was better in the 60s" (or 80s, or 90s) ignores what sucked about those solutions.
1 reply 0 retweets 3 likes -
I don't think anyone here ignores that there were problems with the Smalltalk approach, or is saying "everything was better back then"...
1 reply 0 retweets 1 like -
Replying to @robotlolita @stilkov and
I think the smalltalk approach failed on the merits. I don't want it today personally.
1 reply 0 retweets 1 like -
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 @wycats and
Using an image-based format gives you some good things here, but at the cost of having to reinvent most tools (w/ better experience)
2 replies 0 retweets 1 like
You only get better total experience with sufficient adoption, but https://www.dreamsongs.com/RiseOfWorseIsBetter.html …
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.