The other way E looks to work very nicely is as the "stitching material" for programs written in Java, which will probably be made to run fast before E is made to run fast. I have been looking at my Reversi program (posted on the Web for a couple years now) with an eye to a distributed-computation version--anyone on the Web could start up a copy of the Reversi Computation system and have their computer become a part of the analysis, with an eye to doing a complete solution of the game (alpha-beta-minimax to 60 ply, at which point the game is over). It looks alluringly straightforward to wrap the BoardEvaluator Java class with enough E machinery to just manage the cross-computer communication. Of course, going all the way for the performance freaks in these days before Java runs fast, you'd do BoardEvaluator in C (or assembler! :-) The cost of even current E would be negligible.
From: Mark S. Miller <email@example.com>
To: Chip Morningstar <firstname.lastname@example.org> Cc: email@example.com <firstname.lastname@example.org> Date: Thursday, May 06, 1999 11:55 PM
Subject: Re: Beowulf + E ?
>At 02:49 PM 5/6/99 , Chip Morningstar wrote:
>>Bill Frantz and I were chatting over lunch yesterday and it occurred to me
>>wonder if you have investigated/looked into/heard of the community of
>>doing parallel computation with what they call Beowulf clustering (see,
>Nothing deep. Just a few casual conversations.
>>Second, I'm thinking about the model presented in _Crossing The Chasm_.
>>we should think about more consciously positioning E as the Perl or Visual
>>Basic of distributed systems: its job is not to run fast, its job is to
>>unsophisticated programmers of average competence to quickly and fairly
>>whip together boring but valuable small-to-medium sized (distributed)
>>applications. Being the hardcore hacker early adopter types that we are,
>>*like* to think of what we are doing here as edge-of-the-art stuff, but it
>>be more advantageous to posture as the second wave of technology, making
>>class of systems accessible to the mainstream.
>I quite agree with this last paragraph. The difference between Joule & E
>primarily E's effort to be immediately understandable and familiar to a
>large number of Perl, Python, & VB level programmers; and to enable them to
>casually create working distributed applications, without needing a deep
>knowledge of distributed system foo.
>However, the Internet as a whole is a much bigger laboratory than Beowulf
>clusters, and there's a lot more payoff for a lot more people if they can
>target their distributed app development at the Open Internet. With E,
>shouldn't be harder than targeting a closed Beowulf cluster.
>A good example is MarcS' upcoming Secureit-EChat -- a truly secure 2-person
>distributed chat program in 5 pages of E code, about 3 of which are user
>interface. Watch http://www.skyhunter.com/marc.html
>Of course, if a Beowulf-based opportunity to advance the project presented