https://news.ycombinator.com/item?id=40047094

Comments URL: https://news.ycombinator.com/item?id=40047094

Points: 693

# Comments: 378

The amount of dumb, educated people that blindly accepted everything that was fed to them during the fucking pandemic is driving me up the wall.

"Just two weeks to flatten the curve!"

Latency was exceptionally improved. Web pages felt like the loaded faster and at the very least, users could not tell that they were using an encrypted connection.

The protocol essentially worked using a fast-ACK protocol that would preemptively request retransmits (and was occasionally wrong). This enabled it to use connectionless UDP protocol as the underlying transport mechanism. There is, of course, a cost for reduced latency. That cost was slightly higher bandwidth utilization on the network. This was suboptimal for long-lived streams (media and other downloads) so we tried to fault over to ordinary TCP in these instances.

Hard experience taught us that churn is just crazy high, no matter how compatible it easy to use you make it. Getting tens of thousands of stars is not the hard part because it's such an easy concept to like. But I would be surprised there are more than let's say ten thousand piholes in active use.

More government is rarely the answer and especially so in this case.

I'm really glad I got off that ride.

They aren't standard by any means.

https://archive.org/details/flash-is-dead

Source; I make a living exploiting market inefficiencies.

"In the case of Java volatiles, part of the solution is to force all reads/writes to bypass the local registers, and immediately trigger cache reads/writes instead. As soon as the data is read/written to the L1 cache, the hardware-coherency protocol takes over and provides guaranteed coherency across all global threads. Thus ensuring that if multiple threads are reading/writing to the same variable, they are all kept in sync with one another. And this is how you can achieve inter-thread coordination in as little as 1ns."