Dynabook hw cost

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
42 messages Options
123
Reply | Threaded
Open this post in threaded view
|

Re: Dynabook hw cost

J J-6
>From: Alan Kay <[hidden email]>
>Reply-To: The general-purpose Squeak developers
>list<[hidden email]>
>To: The general-purpose Squeak developers
>list<[hidden email]>,
>[hidden email]
>Subject: Re: Dynabook hw cost
>Date: Tue, 29 May 2007 08:28:23 -0700
>
>Hi  Subbu --
>
>See what you think of the "preposterous proposal" (as one reviewer termed
>it).
>
>http://www.vpri.org/pdf/NSF_prop_RN-2006-002.pdf
>
>One of the ideas here is that you have to work the whole spectrum, but try
>to find qualitative boundaries that can be maintained and will help all.
>
>Cheers,
>
>Alan

Well personally I am very hopeful about this proposal.  I have been thinking
for some time now that it is time to look at a new style of OS, and this
sounds very good indeed.  Do you have funding yet?  When can we expect to
see something we can play with? :)

_________________________________________________________________
Catch suspicious messages before you open them—with Windows Live Hotmail.
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_protection_0507


Reply | Threaded
Open this post in threaded view
|

Re: Dynabook hw cost

K. K. Subramaniam
In reply to this post by K. K. Subramaniam
On Tuesday 29 May 2007 11:18 pm, subbukk wrote:
> Building a 20KLOC monolith would definitely be a challenge. Unix kernel was
> only around 6K lines of C when it started. TinyCC (circa 2004), a
> bootloader that compiles Linux kernel on the fly and runs it, is about 7500
> lines of C. The issue here is not one of space or speed constraints but one
> of verifying correctness of such a monolith within engineering tolerances.
Let me clarify what I meant since the way I phrased the sentence is ambiguous.
I am not claiming that dynabook software can be built in less than 20KLOC. If
our basic unit of assembly is a line of code, then putting together 20K of
them reliably in a way that millions could use it is indeed a challenge. Just
like Smalltalk/Lisp unburdened programmers from tracking memory allocs/frees,
we need better abstractions and separation of concerns. Instead of 20KLOC,
the problem could be factored into two systems of 5-7K each to make it
tractable.

Regards .. Subbu

123