At one brief moment, Dan mentions Fabrik, which is a visual data flow programming model he built at Apple in Smalltalk in the 80s.
http://methodsandmessages.vox.com/library/post/dan-ingalls-interviewed-on-floss-weekly.html
"I have a mind like a steel... uh... thingy." Patrick Logan's weblog.
At one brief moment, Dan mentions Fabrik, which is a visual data flow programming model he built at Apple in Smalltalk in the 80s.
http://methodsandmessages.vox.com/library/post/dan-ingalls-interviewed-on-floss-weekly.html
Bill de hÓra predicts...
if Gears (or something like it) becomes ubiquitous (and it will), then eventually XMPP will become a protocol option alongside HTTP, allowing data to be pushed down into the client.I'm for it. Note Adobe's AIR has all of these things, and then some, not to mention an API for either Flash/Flex or HTML/Ajax-based UIs.
I'd love to see more competion to the browser's current UI programming model, which is still what you are left with after adopting Gears. At least AIR gives you a choice, and Flex is open, so conceivably Google, Mozilla, or whoever could build off of Flex.
(I discount Lively Kernel for the time being. It's probably got more promise than I give it credit for. SVG has a lot of interesting capabilities especially for display, but it's still too clunky for the interactive bits. Kind of like NeWS vs. Display Postscript, ironically.)
Even Flex is so 1990s. There have been several significant improvements on that old MVC-ish model from the pre-web client/server days. Most of them in fact *pre-date* the 1990s adoption of Smalltalk's 1970s MVC. Still Flex is way better than HTML/Ajax for developer countenance though.
But one thing I've wondered is why the fascination with this service
that as far as I know is run by one outfit, has some "issues" (e.g. I
clicked on Mike Herrick's twitter URL the other day and each time saw
nothing but apologies from twitter for failing to work properly), and
is not federated across multiple providers as with, well, the web.
And I've wondered why people don't just use XMPP which is a federated
messaging platform with pub/sub topics etc. Or why not create a
twitter-ish system that can be federated.
So someone just published the source to an erlang-based twitter clone...
http://twoorl.com/
http://code.google.com/p/twoorl
I don't know if this specific clone is the answer, but it begs the question.
Via Signal vs. Noise, the following video is incredibly inventive. The theme becomes tedious for me before halfway, but still... I'd like to see more like this with a better story to tell...