Amadiro

7 ms·

31.
by Amadiro 14y ago
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 brow
32.
by Amadiro 14y ago
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
33.
by Amadiro 14y ago
So... how much memory does it eat?
34.
by Amadiro 14y ago
"twentysize"?
35.
by Amadiro 15y ago
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.
36.
by Amadiro 15y ago
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...
37.
by Amadiro 15y ago
p.s. I'm glad to hear about the addition of the flux capacitor
38.
by Amadiro 15y ago
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 informati
39.
by Amadiro 15y ago
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
40.
by Amadiro 15y ago
"The finisher" sounds like a mythical creature to me...