Others have mentioned protocol ossification which is indeed the primary reason. A secondary reason is that QUIC fuses TLS so its latency is further reduced by one RTT. For high latency networks, the difference is palpable.
It seems to be missing reviews? I have always thought about building my own recommendation engine from steam data, given how steam's own recommendation never works for me.
Every human knows that governments and bureaucracies are inefficient in some way. It's been mocked since the dawn of times. The issue is that you don't toy around with big legacy systems like you do with twitter. To satisfy their little immaturity and get political points on their fans they start ripping off everything without enough time. If they started real medium term efforts to analyze, organize and then migrate it would be different. Plus there are other factors due to human group and political time that will come back later and muddy things up again when someone feels like fixing elon's patch.
I disagree with that, if a system needs time to check, then it's not inefficient, it's right at the speed it needs to be to work. What I'm thinking of is absurd structure beyond the need for checks and balances.
Some examples of "stupid" ineffiency: delegating tech support outside government. Meaning no technician could fix a laptop on-site, their role was to notify a private company to come one day to take the device and come back later with a fix. The delays were bad, and compounded rapidly, the employees couldn't work, citizen wasted days off and had to reschedule a month later.. really bad. Plus technicians skills were unused/wasted, they hated their jobs, and communication with partners was mostly hostile/red-tape adding more friction. They didn't have enough money to change LCDs but didn't allow you to give some even though there were plenty of working ones for free. Same for printers.
This is the kind that needs to be pruned.
Also I believe there's another form of "perfect" government, that is not a mechanical human grinder like a dictatorship: harmonious. It might be a naive dream but .. maybe not.
Depends on how they weigh the cost of a false positive versus false negative decision. The former seems to often be the key focus of a bureaucracy, slowing down the rate of diffusion of new technologies even among willing adopters.
Design docs are critical to your promotion. The boss and the committee do read your design docs, sometimes very carefully. Only your peers and at most your TL read your code.
> the committee do read your design docs, sometimes very carefully
Yadda yadda, that may be true sometimes but that the quality of the doc would get you promoted makes no sense and is also not a good metric. I think most of these committees look at who approved it and what known people thought/wrote in response. I was told in this promo-game to try to get comments from high-level people for this reason. That is more a popularity contest, and less a competition of well articulated ideas.
I think most people here want to improve the way things are. We talk about engineering practice to improve the practice, not to please management or give career advice. Usually, at least.
This is where it happens first. A bunch of engineers (or just generally people with boots on the ground) get together and find better ways to do things. Before agile was mainstream and corrupted beyond recognition, the waterfall model was the way recognized by management and working within that model would have gotten you promoted easier. Things evolve.
I wish I can check a box to say that I'm over 18 and willing to accept any consequences and unshackle the fully potential of AIs. I hate all these safety protections.
I wish I could check a box and say that I'm over 18 and willing to accept any and all consequences of a nuclear weapon so I could finally buy my own nuke.
reply