[Swift-devel] CPU usage with provider-deef
Mihael Hategan
hategan at mcs.anl.gov
Sat Jun 16 15:15:04 CDT 2007
On Sat, 2007-06-16 at 19:52 +0000, Ian Foster wrote:
> I wasn't suggesting (at least in the first instance) that Mihael take the prototype and turn it into production, but that Mihael and Ioan sit down together and do a code walkthrough. I think that this would likely identify bugs and opportunities for simplification.
It's somewhat on the same in level of fun :). From the experience I've
accumulated so far, design is hard. Understanding prototype design is
probably even harder (not only do you need to understand the problem,
you also need to understand why many non-obvious things are done the way
they are done).
Mihael
>
> Ian
>
>
>
> Sent via BlackBerry from T-Mobile
>
> -----Original Message-----
> From: Ben Clifford <benc at hawaga.org.uk>
>
> Date: Sat, 16 Jun 2007 19:36:17
> To:Mihael Hategan <hategan at mcs.anl.gov>
> Cc:swift-devel at ci.uchicago.edu
> Subject: Re: [Swift-devel] CPU usage with provider-deef
>
>
>
> On Sat, 16 Jun 2007, Mihael Hategan wrote:
>
> > On Sat, 2007-06-16 at 12:03 -0500, Mike Wilde wrote:
> > > This should be fun, and a nice break from the I2U2 work that you've
> > > been immersed in, Mihael.
>
> > I have my reservations towards the amount of fun it involves.
>
> Right, taking prototypes and turning them into production isn't
> necessarily fun - in fact, a lot of the fun already happened with the
> making of the prototype and the rest is some what drugery. (to an extent
> that's the same situation i2u2 cosmic was/is in).
>
More information about the Swift-devel
mailing list