3 ms·
This principle was very well used in Smalltalk's IDE in its Class Hierarchy Browser. Some other languages can exploit it too. And some clever web-based REPLs a
by sebastianconcpt 4y ago
This principle was very well used in Smalltalk's IDE in its Class Hierarchy Browser.
Some other languages can exploit it too. And some clever web-based REPLs approximate decently to it.
I'd love to see this idea growing outside the Smalltalk world because is very valuable and influential to the DX (developer experience).
I vaguely remember seeing it in IBM's Visual Age for Java in the early 2000's.
- g051051 4y ago> I vaguely remember seeing it in IBM's Visual Age for Java in the early 2000's. Yes, it was pretty amazing.
- sebastianconcpt 4y agoI've heard it was implemented in Visual Age Smalltalk.
- g051051 4y agoYes, and it ran Java on their "Universal Virtual Machine": https://news.ycombinator.com/item?id=32433429 https://news.ycombinator.com/item?id=32433429
- pasc1878 4y agoYou can use this view of java code in Eclipse as well. But VAJ was still better.
- sebastianconcpt 4y agoBetter in what? Refactoring tools or? Oh, if I'm recalling correctly, it had workspace for live scripting and it could inspect the objects returned by snippets as Smalltalk could?
- HelloNurse 4y agoI've actually used Visual Age for Java, and its "repository" was an existential threat. It was basically incompatible with revision control (a gigantic binary blob) and it could be corrupted, for example (true story) by exceeding some maximum repository file size.