Loose type checking in E
Tyler Close
tyler@lfw.org
Wed, 14 Oct 1998 07:56:58 -0400
>Date: Wed, 14 Oct 1998 05:47:12 -0400
>To: "Mark S. Miller" <markm@erights.org>
>From: Tyler Close <tyler@lfw.org>
>Subject: Re: Loose type checking in E
>In-Reply-To: <3.0.3.32.19981013220337.006f5174@mail.erights.org>
>References: <3.0.6.32.19981012220448.009221f0@www.lfw.org>
<007e01bdf618$74131ea0$63fcadcf@marcs-mobile>
>
>At 10:03 PM 10/13/98 -0700, you wrote:
>>At 10:04 PM 10/12/98 -0400, Tyler Close wrote:
>>>Be careful with how far you take your operating system resources analogy.
>>>There is no inherent tree structure to distinct resources in an operating
>>>system. There is, however, an inherent tree structure to a GUI.
>>
>>Indeed. Doesn't this suggest that you should be careful in generalizing
>>from the tractability and beauty achievable in concurrency control for GUIs
>>to that achievable in general?
>
>Wow, how many hours ago was it that you were going on about generations of
fruitless labour for a multithreaded GUI library?
>
>I'm proud that you approve of my design though.
>
>Please remember that the original reason for me mentioning my GUI library
was as a counterpoint to your "unworkable" assertion and your particular
criticism of multithreaded GUIs. As for the general, I have designs for
other situations as well.
>
>>>>Strange but true stories of the antiquity of computing :-)
>>>
>>>We're still in the antiquity of computing ;)
>>
>>Indeed. Even more so than we were in the late 70s / early 80s :(
>
>I'll have to take your word for it, but Design Patterns was a 90s
phenomenon and E is currently being written.
>
>ciao,
>Tyler