Once you reach scale, Ruby can be a limiting factor depending on how much latency impacts your revenue. And it's not so easy to remove that dependency as I've seen.
Rails can easily serve up pages in <100ms. If you do have an endpoint that is CPU-bound to where you can’t meet your SLA goals, you can serve up just that endpoint in Rust or Golang. But that’s rare.
Usually what happens at scale is that the SQL database starts slowing down as more data is loaded in. Partitioning, indexes and painful refactorings aren’t prioritized. Engineering will champion “a faster language”—that incidentally allows them a new data model where they add in proper indexes at the start. They aren’t really incentivized to realize they could see the same gains by just improving their existing data inside the Rails monolith.
Source: experience improving performance (including latency) with multi-billion-dollar Rails monoliths
> Finally, the Federal Reserve Board on Sunday announced it will make available additional funding to eligible depository institutions to help assure banks have the ability to meet the needs of all their depositors.
That sounds a lot like some type of bailout to me. What does "make funding available" mean? Where does that funding come from? It's going directly to banks, not to depositors. How does that work?
And also we probably don’t want to say “haha silly SVB customers, they can wait ten years to get their money back” because none of us want to live in a world where most Americans, most of whom don’t understand all these complexities, start runs on ALL the banks because they think this is the start of a collapse. It becomes self-fulfilling at that point.