By this way of thinking everything is vital for "security purposes" and you end up with a full autarchy. Food is vital because you can't rely on others to feed your population. And so is energy. And so on. What is really going on though is that the US started a trade war with China and it's just another salvo in this war. Soon the US will declare electric cars from China as a "threat" and ban them, too. Probably the Chinese will retaliate with banning Teslas. On the same grounds, too.
Actually it's not universally true that people working closely together know who is competent and who is not. Because you yourself need to be competent to know if others are doing a good job or not. If you are surrounded by incompetent morons you as likely might be labeled as incompetent by them and since they are the majority you lose the battle. It doesn't even have to be done on purpose by the morons, they just don't know they are bad at what they are are doing and create a kind of a circlejerk re-assuring themselves
another explanation - they did test it in other scenarios but the results were against their hopes so they 'accidentally' omitted such tests in the 'official' test suite. Very common tactic, you massage your data until you get what you want.
Modern mobile networks use exactly the same protocol to carry voice and data. Because voice is just data. When your call is fading or being intermittent then the packets are being dropped. In such situation packets of your mobile data for instance a web page being loaded by a browser are also being dropped. Mobiles drop packets left and right when reception deteriorates or there are too many subscribers trying to use the shared radio channel. And HTTP2 or 3 can't do much about it because it's not magic, if you lose data you need to retransmit it which TCP and HTTP/1.1 can do just as well. BTM UMTS which you claim you were so professionally involved in also uses converged backbone and carries both data and voice the same way so you should have know it already lol :)
You wouldn't force a girl to date you because you know it's not rational. You wouldn't force kids to play with you because it's not rational either. Simple as that. Just because somebody thinks it is actually rational doesn't make it so. The kid wasn't rational at all, if anything his behavior was completely irrational
You made a claim that packet loss in mobile networks is not a common occurrence. This claim is patently wrong and anyone with a smartphone can see for themselves.
Everyone who is using a phone knows that what you are saying is not true. Otherwise we would not experience dropped calls, connection resets and mobile data being unavailable. Mobile networks are unreliable and you can't paper it over with some magic on TCP or HTTP2/3 level.
EDIT: better yet, anyone can just use network tools on their smartphone to see for themselves that mobile networks do drop TCP packets, UDP packets and ICMP packets very freely. Just check yourself!
No matter how you try to explain it, trying to force other kids to play with you is not a rational behavior. Rational behavior would be trying to find out why they don't want to play with you and try to do something about it. Would you say that if a girl doesn't want to date you then forcing her to date you is a rational behavior?
They didn't fail. They got their promotions. It's you, the end user, who is left holding the bag. But fear not, HTTP3 is on the horizon and this time it's going to be glorious!
The parent is just moving goal posts. The whole idea behind multiplexing data streams inside a single TCP connection was that in case of a packet loss you don't lose all your streams. But it doesn't work in practice which is not really surprising when you think about it. When you have multiple TCP connections it's less likely that all of them will get reset due to connectivity issues. Whereas with data multiplexing when your single TCP connection is reset all your data flow stops and need to be restarted.
Yeah HTTP/2 push is so great that Chrome removed it.
Straight from the horse mouth: "However, it was problematic as Jake Archibald wrote about previously, and the performance benefits were often difficult to realize"
https://developer.chrome.com/blog/removing-push