They write the following reason in the article:
But as the web and other internet technologies mature, certificates are starting to be a requirement in order to unleash functionalities, especially in web browsers, such as the faster connection protocol HTTP/2 and payment processing.
As for point 1) I fully agree. I'm using it a lot currently due to lack of alternatives, mainly with java. Swagger codegen is the one I've had most success with, but both openapi and swagger codegen shares the same problems.
For internal projects we use grpc which is a breeze to use in comparison.
"The response was swift, and it came from starred chef Antonello Colonna. The Roman cook rejected Parisi's solution, claiming that with this procedure the pasta becomes "rubbery", and impossible to serve in a high-level restaurant. Colonna considers the method a failure and proposes cooking on an open-fire grill, with pots that have fed entire generations like a cauldron. The chef claims this traditional low-temperature technique lowers electricity costs in his restaurant."
Did a brief scan of the repo. Looks like a lot of it comes from adding new headers. This commit adds +#include <linux/wait_api.h> to 1627 files for instance.
Getting everything back up again will probably be a nightmare. Imagine all the internal services trying to reach a consistent state after such a long outage.
In the long run it would've. It was mandatory to pay if you owned a TV. They tried to collect it for people having laptops / mobile phones but it was ruled illegal in the courts.
Instead the government replaced it with a new tax which seems more fair.