Amadiro

Well, WebSockets are somewhat more efficient in terms of overhead, the latency will probably be a little better, can be handled more efficiently/easier on the server-side and it doesn't have the other drawbacks Comet has (AFAIR in some browsers, say, opera, if you use comet, you've basically used up your quota of allowed connections, so making additional XHR might be problematic.)

Boards for high-end FPGAs like that are not cheap to make yourself either (needs like 6 layers or more, because they have SO MANY densely packed pins + you need one or two layers to feed its gratuitous hunger for power), so you'll probably end up having to buy some ready-to-use solution that probably quadruples that price...

So... how much memory does it eat?

"twentysize"?

Additionally, AFAIK, stackoverflow started out as .net/C# community, so they're probably somewhat biased towards that. To remove such bias, you'd probably need to analyze at least a few dozen such forums.

I was also staring at the title for half a minute, puzzled as to what's the deal about failing to designing a CPU with a megaflop...

p.s. I'm glad to hear about the addition of the flux capacitor

I'm mainly referring to the article here, which is rather ambiguous and mis-stated in its wording, as well as the submission title, which is entirely missing the point of what Fabric does. I don't doubt that you have more in-depth information on your site, or that, for that matter, using Fabric from your scripting-language of choice can actually speed up your code (considering things like Cython have existed for a while.)

Reality check:

[x] Claims to support a multitude of languages with wildly varying semantics while still achieving some goal that seems unrealistic (or thus-far un-achieved) even for a single one

[x] Claims to achieve performance similar to C/C++/fortran/some other traditionally-considered-fast language

[x] Claims that some traditionally-considered-hard-to-do-task will now become easy

[x] Uses buzzwords like "in the cloud"

[x] Shows meaningless benchmarks without context, code or an in-depth look at the actual bottlenecks of the benchmarked code, suggesting the particular solution by far exceeds all the competitors

[ ] Extensive usage of the words "flux capacitor" or "Gigawatts"

"The finisher" sounds like a mythical creature to me...