It's worth mentioning hard acceleration causes a torque multiplication to occur in torque converters vs a slow acceleration does not (check me on that). Once locked up, multiplication no longer occurs. Thank you hot rod magazines of the 90's.
This line of thinking is utterly bizarre to me. People need to stop thinking of GitHub as anything other than a typical corporation. If they could charge an additional dollar they would keep it for themselves.
This is what happened during the last major downturn. There was an influx of startups. If you want to stay in tech during a downturn you either start a business, join a startup, stay in school or switch industries. What you don't do is stay unemployed for years on end. Best of luck to all of those trying to navigate this difficult situation.
I suspect you've also had zero reason to use the vast majority of programming languages at work in any meaningful capacity outside of the normal top ones. That's normally how tech decisions work. That certainly doesn't negate the possible benefits of other languages.
Others use Erlang and Elixir quite effectively and successfully in several billion dollar businesses apart from nerd aspects. It will be interesting to me personally if Gleam also has its day in the sun.
I don't disagree with that call out. However, we've been through these discussions many times over the years. The solid queue of yesteryear was delayed_job which was originally created by Shopify's CEO.
Shopify however grew (as many others) and we saw a host of blog posts and talks about moving away from DB queues to Redis, RabbitMQ, Kafka etc. We saw posts about moving from Resque to SideKiq etc. All this to day storing a task queue in the db has always been the naive approach. Engineers absolutely shouldn't be shocked that approach isn't viable at higher workloads.
