News for hackers. Stuff that matters.
Re:Do not do in code what can be done in infrastructure (2017) by nijave on Friday August 13, 2021 @01:26PM (#28171828)
It seems like one of the easiest to explain to non technical end users. "Yeah, you see we've measured the amount of time it takes a piece of information to move over the longest wire. Then we've calculated the length of your wire and determined the difference. We added that to this piece of code written in (proceed to lose most non technical users)..."

Vs "yeah everyone's wire is the same length"

Which is fairly easily provable

Re:Do not do in code what can be done in infrastructure (2017) by kasey_junk on Friday August 13, 2021 @04:54PM (#28174381)
Every exchange that I know of that provides collocation has contracted standard length cable routes as part of the offering. So that’s not the gimmick.

The gimmick that IEX brought to the table is that they are delaying orders a fixed amount. They own the matching engine so can trivially add that fixed amount in code.

But that’s not nearly as fun to show off as a big box of spooled fiber.

Re:Do not do in code what can be done in infrastructure (2017) by shapefrog on Friday August 13, 2021 @05:47PM (#28174971)
I am sure there are still plenty of lawyers lined up with tape measures to check that the opposition doens't have a smaller one than them.