How does loom address backpressure?

The same way synchronous code always has: by blocking. Blocking queues with or without buffers offer sophisticated forms of backpressure (with different levels of "slack"). Backpressure in synchronous code is a problem that was solved long, long ago. It only required special handling in asynchronous code.

By scheduling virtual threads in an intelligent order.

Most companies are dinosaurs, you are delusional to think otherwise.

Software is usually not worth much without the data it operates on.

Azure has tons of Microsoft-entrenched enterprises where discounts on Office 365 are a valid argument for choosing the entire cloud stack.

Why would you insulate inner walls of a building?

So you don't have to hear your neighbors having sex.

Thermal and acoustic insulation are a different thing.

To avoid heat transfer between rooms that people want at different temperatures

Fireproofing? (Really fire resistancinh)

Folding bikes are much more expensive, especially electric.

It's a lie, there is no provision whatsoever for people getting paid in GDPR.

It is much harder when you are working with other people and need to learn everyone's "tiny libs".

And how much of their codebase is this? 0.5%, if that?

Sarcasm carries poorly over text :)