2,457 karma · joined February 13, 2011
Node has both blocking and async versions of a lot of IO operations. But async IO is more commonly used certainly. The real question might be whether a thread pool backed async IO implementation makes your program do concurrent IO better than a GIL + blocking IO calls that release the GIL, it's not obvious to me.
(Doesn't Node have threads too nowadays?)
At some point we'll have to migrate to new terms for "in hardware" for offloaded operations since we are no longer using fixed function hardware :)
Taxing fossils yields revenue that has to be used for thngs like income transfers or breaking dependency on fossils to offset these steps back.
1. We drastically reduce fossils using regulation / legislation, in which case they become harder to get (eg more expensive) than the alternatives for most users.
2. We don't reduce fossils, in which case we're left with just trying to outcompete energy supply so nobody wants to pump the cheap oil and gas from the ground anymore.
Option 2 is never going to work and is equivalent to just giving up on fighting climate change.
What % of engineers at Mozilla are in SV and other places where Mozilla competes with FAANG? I thought quite a lot of the employees were remote all over the world.