Making our code public would have been ideal. The problem was that we
don't know how the system should look like, and things have gone so
many iterations. In a way, I regret that we couldn't do a good job
making code public, but in other ways, I'm glad we didn't as we did
not have to feel bad abo
I cannot address "report card". I have greatly enjoyed the papers and
respect the aspiration to deliver a system in ~20kLOC by leveraging
algorithms and Moore's law. A system, with size and elegance, that folks
could get their head around.
Your point on discussion of what has already been publis
On Fri, Apr 19, 2013 at 1:51 PM, Casey Ransberger
wrote:
> I wanted to send this message out after the final status report, but since
> that's indefinitely delayed (keep going!) I'm just going to do it now.
>
> Easy question: has keeping this dialogue open been useful to the folks at
> VPRI, or
s VPRI folks and all of you posters!
>
> Regards,
> Paul Odle
>
> --
> *From:* Casey Ransberger
> *To:* Fundamentals of New Computing
> *Sent:* Friday, April 19, 2013 3:51 PM
> *Subject:* [fonc] Report Card
>
> I wanted to send this message out after the final st
VPRI report. And a binary build of FRANK maybe?
Thanks VPRI folks and all of you posters!
Regards,
Paul Odle
From: Casey Ransberger
To: Fundamentals of New Computing
Sent: Friday, April 19, 2013 3:51 PM
Subject: [fonc] Report Card
I wanted to send this
I wanted to send this message out after the final status report, but since
that's indefinitely delayed (keep going!) I'm just going to do it now.
Easy question: has keeping this dialogue open been useful to the folks at VPRI,
or has it been more of a burden than anything else?
I can definitely
