stompin

4 ms·

1.
by stompin 10y ago
> "One proposed method of stopping incidents like the Knightmare, and generally to limit HFT from wading too far into ethically grey areas, is by leveraging blockchain tech. For example, front-running—sneaking in trades a few micros
2.
by stompin 10y ago
To answer the question "why use your own microwave network?" the author provides 2 reasons: > The first reason is somewhat obvious; if you have your own network connection, it's usually easier to guarantee things like secu
3.
by stompin 10y ago
Since when is having an opinion a bad thing? If we all delayed putting out theories (like Good to Great does in explaining commonalities of companies that made it huge) until all existing theories like Survivorship Bias were covered then n
4.
by stompin 10y ago
and moves and copies won't have potential for other memory management bugs? You'll still have memory management overhead and now additional complexity.
5.
by stompin 10y ago
do you really need coroutines for cert decoding and handling of handshake messages? It's not like you can parallelize these things and do something else in the meantime...
6.
by stompin 10y ago
Is there any evidence that memcpy/memmove outperform malloc?
7.
by stompin 10y ago
Given various clues such as: -"OS-less" -small memory footprint -going out of their way to include discussion of legal jurisdictions -the author and past activities -performance seems not a major concern Makes me suspect that a ma
8.
by stompin 13y ago
> older style perl code some bad advice here based on bad assumption. You assume and suggest that going with another "modern stack" is somehow going to be worth the extra effort. Re-inventing the wheel is a recipe for wasting
9.
by stompin 13y ago
given the years of covert actions slowly coming to light, this is changing. I'm not just talking about relationships with 3-letter agencies but also actions like colluding to push down developer salaries, black-boxing their search alg