The Web Is Becoming Smalltalk
21–30 of 112 posts
Re: The Web Is Becoming Smalltalk
#22Chris Granger's Light Table is also trying to do it. Of course, Bret Victor's talk breathed new life into this whole thing. But everything old is new again. People want to build software from a small kernel that scaffolds itself. They want to immediately switch between "testing the app" mode and "building the app" mode. They want something more than a text file, a tool pipeline, and an executable at the other end. On…
I can't help but smile while I watch.
Re: The Web Is Becoming Smalltalk
#23Re: The Web Is Becoming Smalltalk
#24Chris Granger's Light Table is also trying to do it. Of course, Bret Victor's talk breathed new life into this whole thing. But everything old is new again. People want to build software from a small kernel that scaffolds itself. They want to immediately switch between "testing the app" mode and "building the app" mode. They want something more than a text file, a tool pipeline, and an executable at the other end. On…
[1] John Maloney got it with Morphic, and even coins the term Liveness at about the same time Tanimoto does. However, this was originally in Self and relatively independent from Self's hot swapping capabilities. It also didn't really map back to code very well (it was very dependent on direct manipulation via Morphic's edit menu).
Re: The Web Is Becoming Smalltalk
#25WebDAV? Heaven help us…
Why the dislike? It's not a bad protocol.
WebDAV had some varying levels of support in Windows and Mac desktops. But AFAIK the Windows stuff got broken; not sure about Mac. I think that access from a GUI file browser was one of its main use cases in the 90's. If nobody does that anymore, and I don't think they do, then the protocol will need a new app or it will continue to die.
Re: The Web Is Becoming Smalltalk
#26This kind of hot-swapping can be achieved on quite a few languages; certainly Perl and Ruby in addition to JS, and I'm sure there's a dozen more languages that allow you to redefine at runtime. The difference is that Smalltalk made hot-editing the default. SmallTalk is an uncommon language these days, with the exception of its half-descendant, Objective-C. Ruby borrows Smalltalk's OO semantics pretty much completely.…
You can even do it in Java with Eclipse (Notch did it during his screencast), although I don't know the specifics.
Re: The Web Is Becoming Smalltalk
#27This kind of hot-swapping can be achieved on quite a few languages; certainly Perl and Ruby in addition to JS, and I'm sure there's a dozen more languages that allow you to redefine at runtime. The difference is that Smalltalk made hot-editing the default. SmallTalk is an uncommon language these days, with the exception of its half-descendant, Objective-C. Ruby borrows Smalltalk's OO semantics pretty much completely.…
You can even do it in Java with Eclipse (Notch did it during his screencast), although I don't know the specifics.
Re: The Web Is Becoming Smalltalk
#28Treat every web site or address or endpoint as an object. Allow message passing as though the web were simply a single object-oriented system resident on the same computer. The definitions of the APIs are kept as standard, so the system "just works" with any site.
This is, of course, the vision of APIs. But could we do better? Could we make it closer to a true object-oriented system, even simpler to use? Not sure if it would make a big difference, but as we know, sometimes a simple thing that makes connections easier can make a huge difference (eg: XmlHttpRequest).
Make the web as easy as smalltalk. For every API, and eventually, every site. Not just the ones we decide to make language-specific libraries for. One library per language just interfaces with "the web" as a fully-generic API you can access as easily as any object.
Just thought I'd share this thought. Any thoughts or ideas?
Re: The Web Is Becoming Smalltalk
#29It's a little surprising how much we keep reinventing.