[Python-ideas] Message passing syntax for objects

[Masklinn]

On 2013-03-18, at 20:06 , Georg Brandl wrote:
> 
>>>>> "http://www.cnn.com" >> MyInternetObject  #outputs the HTML text from CNN's home page.
>> 
>> Each object has to figure out how it will receive things from outside
>> of it.  Things it can't handle (a string sent to an int) just have to
>> be dropped to some other space, much like stderr does within the O.S.
>> 
>> There are probably many other very interesting examples, but the key
>> idea I'm working on (as noted in other messages), is a sort-of
>> universal language for the internet, a WebOS to be applied to a
>> universal data model.
> 
> It seems that you are reinventing pipes (such as UNIX shell pipes).
> I agree that as a model for handling data the pipe paradigm is elegant,
> but only as long as you deal with simple data of a single kind (such as
> strings in the UNIX world).  But make the data complex enough, and it's
> an instance "all problems look like pipes if all you have is a vertical
> bar".

Or you start tagging your messages (since the messages are apparently
structured not byte-streams as they are with unix pipes) as is done in
Erlang, the end-result mostly being to remove a (useful) bit of syntactic
sugar. Unless the messages become asynchronous, then I guess you get
actors?