There is a good reason: teaching yourself not to over-engineer, over-provision, or overthink, and instead to focus on generating business value to customers and getting more paying customers. I think it’s what many engineers are keen to overlook behind fun technical details.

Coffee is an acquired taste, I think. People conditions themselves to like the bitter taste of coffee over time. I remember hating the taste of coffee (or beer, for example) in childhood.

How is this a counter-argument? I often read this, as if there's some international trusted organization of logical thinkers that has approved inclusion of slippery slope to a list of logical fallacies that must never be invoked in a conversation.

Every single time five years later it turns out that the slope actually was slippery.

I’d guess that the target audience would argue that real lossless music experience requires high-bandwidth wires, and is not possible over the air without degradation.

1) it's not cheap to produce lidars at a stable predictable quality in millions;

2) car driving training data sets for lidars are much scarcer (and will always be much scarcer due to cameras' higher prevalence) and at a much lower quality;

3) combined camera+lidar data sets are even scarcer.

Then again, it's good that we have self-driving companies with lidar and without — we will find out which approach wins.

Isn’t it literally the God’s preference of a country for this place and time, from both secular and religious points of view?

Or every country has resources, and weak countries are those that prefer to sell them for cheap rather than work on making use of them?

Instead, the TCP socket must be treated as a stream of bytes, and use either some delimiter as message boundary (like \n, while escaping any newlines inside JSON), or write message size before the message bytes itself, so that the code knows how many bytes to read until full message is read.

Edit: to clarify, TCP protocol does not guarantee that if you write some bytes in one go, they will be read in one go as well. Instead, they may be split into multiple “reads”, or glued together with the preceding chunk, or both. It’s a “stream of bytes” protocol, it only guarantees that written bytes come one after another in the same order.

So the “naive” message separation used in code above (read a chunk and assume it’s the entire message that was written) will work in manual tests, and likely even in local automated tests, but will randomly break when exposed to real network conditions.

Ah, so your idea is the good old “only the emperor who controls the violence apparatus should have a lot of money and power”?

It’s not a very original idea, and it has been tried many times, and it failed many times.

> but then we should be even more careful who gets to the top

Right, so “for some reason only the greedy power hungry psychopaths get to the top in the current system — let’s fix it so that there can’t be many of them, only one government who has power to take away other people’s wealth and concentrate it immensely, surely we will figure out how to make sure it’s not filled with greedy power hungry psychopaths as we go”