7 ms·
It's remarkable (or depressing) how many of the points in the article that are addressed by Smalltalk -- and yet out of reach because in most environments Small
by e12e 13y ago
It's remarkable (or depressing) how many of the points in the article that are addressed by Smalltalk -- and yet out of reach because in most environments Smalltalk is just another program, rather than used as the environment in which we do everything.
It includes things like a source browser that allows looking up ways to deal with eg: email, if you have the/some source code, you can easily run it, a built in debugger and a tight write/test/fix-loop etc.
- seanmcdirmid 13y agoMost of what was Smalltalk has been adopted into modern IDEs (edit and continue, class browser, graphical debuggers, object-oriented programming). Now we are beginning to move beyond Smalltalk; e.g. Smalltalk never provided very powerful search facilities, real live programming, or speculative execution.
- e12e 13y agoHow did Smalltalk not provide "real" live programming?
- seanmcdirmid 13y agoChange your code in smalltalk, say from "w color: black" to "w color: red". And even though the code of the program is "changed," nothing happens because the modified statement is not automatically re-executed. In a live programming system, you get useful feedback about your code edits, not just "fix and continue," and so you would immediately see affected widgets go from being black to red. Chris Hancock's dissertation [1] is really good at making this point: > And yet, if making a live programming environment were simply a matter of adding "continuous feedback," there would surely be many more live programming languages than we now have. As a thought experiment, imagine taking Logo (or Java, or BASIC, or LISP) as is, and attempting to build a live programming environment around it. Some parts of the problem are hard but solvable, e.g. keeping track of which pieces of code have been successfully parsed and are ready to run, and which ones haven’t. Others just don’t make sense: what does it mean for a line of Java or C, say a = a + 1, to start working as soon as I put it in? Perhaps I could test the line right away—many programming environments allow that. But the line doesn't make much sense in isolation, and in the context of the whole program, it probably isn't time to run it. In a sense, even if the programming environment is live, the code itself is not i.e. Smalltalk code simply isn't live. [1] http://llk.media.mit.edu/papers/ch-phd.pdf http://llk.media.mit.edu/papers/ch-phd.pdf
- e12e 13y agoThanks for clarifying -- I'm still not sure which environments are much "more" live than Smalltalk. If you do make changes, usually that code will be executed on the next call? Or are you talking about some strict old Smalltalk-80? While you could change a parameter like color in some text-representation of the live code, wouldn't it be more natural (in Smalltalk) to simply change the object [ed: object instance] in question (and see the immediate change)? I'm considering things like: http://pharo.gforge.inria.fr/PBE1/PBE1ch7.html#x32-111006r228 http://pharo.gforge.inria.fr/PBE1/PBE1ch7.html#x32-111006r22... If Smalltalk allows editing values of variables of running code, and hot code loading -- what is missing? Is it the fact that other systems define the source code as "the truth", and consider the byte/compiled code to be a "secondary artefact" that causes (my) confusion? Because as far as I can tell, Smalltalk does allow you to manipulate the objects that make up your system live?
- seanmcdirmid 13y agoDirect manipulation of the program's state (as opposed to writing/editing code that changes the state) is always live of course in any language. So ya, Smalltalk objects are "live", but Smalltalk code is not. So when Hancock invented this term called "live programming" back in 2003, he was focusing on the code (keep in mind, this work exists in a world where Smalltalk is well known, the Morphic paper came out in 1995, and Seymour Papert of Mindstorms/Logo fame is Hancock's adviser). The problem with editing the program's objects directly is that it is not very powerful in its capability: fine if you want w to always be red, but not fine if their are a hundred w's to edit individually, or if w is red because of some kind of active condition. In any case, hot code replacement doesn't really help either; its useful for sure, but the next step is to change the program's state retroactively [1] to match the new code. Smalltalk never went there, and probably couldn't given the hardware constraints of the time. But now, I think we can go there. The Pharo folks are claiming that their system supports live programming capabilities, but it is just the same old live object/fix-and-continue features that Smalltalk has had for ages. I suspect that they just really don't know what live programming means, and are latching onto the word because its "trendy." [1] http://dynamicaspects.org/blog/2012/08/15/changing-the-past-in-open-systems/ http://dynamicaspects.org/blog/2012/08/15/changing-the-past-...
- e12e 13y agoIt's too late for an edit, but looking at the article again, especially the conclusion, I wonder even more about the seeming dismissal of Smalltalk: > * storing code in a networked database with version control and realtime sync This sounds a lot like Monticello and/or what Lively Kernel does over Webdav? > * a structured editor to enable rich ASTs with unique UUIDs I'd say something similar is achieved by Smalltalk with it's view that there is no "source code" -- there is only the compiled code that is also viewable/editable as text (this is not so much about code, but a feature of a truly object oriented system). > * managing environments declaratively so that evaluating code is always safe I don't see how "evaluating code" can "always" be safe? Or is this similar to having the ability to deploy a separate dev-image in Smalltalk terms? > * a uniform (logical) data model where every piece of state is globally addressable One example of this would be an object graph? > * a model for change that tracks history and causality I take it this is the "live programming" bit discussed alongside here. If all input and output is via messages, it would seem feasible to simply log messages (possibly collapse some messages (ie: +1, -1, +1, -1, +1 becomes just "+1"). > * a powerful query language that can be used for querying code, runtime state, causal graphs, profiling data etc I'm not entirely convinced we need a "powerful" query language. But something to specify context (show me all counters in the date widget) would be good -- but it would be fine to express it as "in:someDateModule var:count". Maybe I just read "powerful query language" differently than the author (intended). > * composable gui tools with transparent guts We seem to be reinventing these forever. > * a smooth interface to the old world so we don't end up sharing a grave with smalltalk I really didn't want to go all "Smalltalk did that" (I'm not even sure it did I only know new-ish Smalltalks) -- but I think the eco-system is in the process of proving the death-by-different wrong: We use Apps on phones and through the web -- and the fact that eg: Google spreadsheets has pretty a pretty crappy interface with "the old world" doesn't seem to bother anyone. I mean, yeah, we know that we probably need to interface with some form of external file system -- but now we can pretty much just throw http/dav at the problem. I guess I'm just grumpy -- arguably there's no difference between running a javascript vm on bare metal vs running a Smalltalk system on bare metal (except for the language part, but we can implement the language(s) we need on top of js anyway…). I just can't help but feel we might do better with a system better designed to be a system, rather than the web browser that accidentally became a vm and virtualized display driver. It doesn't strike me as likely that we'll see a proper security model that actually works for javascript in the near future, for example.