On the other hand, I wish it were a more formalized process rather than this politicized "our president made a deal to save america!" / "Intel is back and the government is investing BUY INTEL SHARES" media event. These things should follow a strict set of rules and processes so investors and companies know what to expect. These kind of deals should be boring, not a media event.
I would argue it's sorta related to Greenspun's tenth rule: https://en.m.wikipedia.org/wiki/Greenspun%27s_tenth_rule
Of course, you'll probably retreat and say "Go is better for small projects", but every large project started as a small one, and it's really hard to justify rewriting a project in a new language in a business context.
Regarding your IDE issues- I’ve found the new wave of copilot/cursor behavior to be the culprit. Sometimes I just disable it and use the agent if I want it to do something. But it’ll completely fail to suggest an auto complete for a method that absolutely exists.
This is a really anti-intellectual take. All of software engineering is about building abstractions. Not having abstractions makes the structure less easy to understand because they're made implicit, and forces developers to repeat themselves and use brittle hacks. It's not a way to build robust or maintainable software.
With PoS protocols, >33% is usually when you have the ability to inhibit finality, which may be what you're thinking of.