<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Eli Barzilay wrote at 01/14/2011 09:21 AM: <blockquote cite="mid:19760.23536.638878.759482@winooski.ccs.neu.edu" type="cite"> <pre wrap="">9 hours ago, David Nolen wrote: </pre> <blockquote type="cite"> <pre wrap="">With a good FFI it seems like someone could write a great Racket DSL for evented network programming a la Node.js minus all the JS callback cruft. </pre> </blockquote> <pre wrap=""> I know very little about it, but it looks like it covers stuff that racket includes as built in functionality. </pre> </blockquote> <br> Yeah, I don't know Node.js, but most of <a class="moz-txt-link-rfc2396E" href="http://nodejs.org/api.html">"http://nodejs.org/api.html"</a> looks like ways to make JavaScript more easily do things that Racket already does better than Node.js does.<br> <br> Regarding event-driven API like I see in the documentation for Node.js "net.Server" documentation, you could implement that in pure Racket pretty easily, without needing FFI.<br> <br> I've done some fairly high-performance I/O for TCP and interactive subprocess pipes in pure Racket.  Racket's own event conception, buffer operations, and multithreading have been up to the task.  Of course, Racket certainly lets you implement simpler abstractions like Node.js's atop this.  You can even make Racket special-syntax like "define-Node.js-like-server-and-with-some-static-checking". :)<br> <br> <div class="moz-signature">-- <br> <a class="moz-txt-link-freetext" href="http://www.neilvandyke.org/">http://www.neilvandyke.org/</a> </div> </body> </html>