The trade off has changed over time as memory access has become a bigger and bigger bottleneck. But caring about this is still "premature optimisation".
The claim of 20x program performance difference is overblown. Compilers can often remove virtual function calls, JITs can also do it at runtime. Virtual function calls in a tight loop are slow but most of your program isn't in a tight loop and few programs have compute as a bottleneck.
Measure your program, find the tight loops in your program and optimise that small part of your program.
* $200-400 million for equivalent onshore wind (they don't mention offshore wind which is more cost effective over it's lifetime)
* $1.5 billion for the SMR
Assuming solar and wind stay the same price for the next decade (which they definitely won't) that's a 4-5x construction price difference. The article didn't mention lifetime, decommissioning or running costs, which is likely a significant difference too.
If you have any unauthenticated routes that you don't want arbitrary websites calling.
> using JWT in a typical SPA <-> API scenario.
Is this typical? It's a pretty horrible setup.
Cookies have a lot of great features that 'store a JWT in LocalStorage' just doesn't have.