resume capabilities

[Kragen Sitaker]

Jonathan Shapiro writes:
> > Maybe it's premature to be worrying about stuff like this when the OS
> > doesn't run Emacs yet.
> 
> Kragen:
> 
> This sort of statement really isn't helpful. I don't see you making any
> effort to port emacs or build a networking stack. I don't see you putting
> up any money to have me do it.
> 
> If you don't care enough to help get the work done, you will just have to
> be patient while I find somebody who will pay for the work, or some means
> to do it in my spare time without having my employer own it, or some
> employer who is willing to let it be published in open source form.

I think you misunderstood my statement.  I was simply thinking of the
way Unix was written --- it started out as a very minimal system with
an architecture good enough to permit extension, but the actual
extension didn't happen until it was needed.

The result was that the Unix extensions were well-designed; easy things
were easy, and hard things were usually possible.  The other result is
that the basic stuff got whipped into shape long before luxuries like
memory-mapped files, file locking, and interprocess communication were
added.

So what I meant was not that EROS sucks because it's not finished yet
--- I don't think it does.  I meant that speculating about how to
design things we don't yet need is generally unproductive, and I hoped
I wasn't doing that.

I don't want to commit to doing stuff for EROS yet, because I don't
want to disappoint people if I fail to deliver, but I do think EROS is
extremely important for the future of civilization and the rule of
law.

About funding:  Have you looked at cosource.com?  If I'm employed, I'd
certainly be willing to contribute a few hundred dollars to getting a
networking stack running.


<kragen@pobox.com>       Kragen Sitaker     <http://www.pobox.com/~kragen/>
The Internet stock bubble didn't burst on 1999-11-08.  Hurrah!
<URL:http://www.pobox.com/~kragen/bubble.html>
The power didn't go out on 2000-01-01 either.  :)