Actually, both.
Perimeter dead hand system algorithm:
1. If perimeter have been activated
2. AND there is nuclear explosion at russian territory
3. AND there is no connection to commander-in-chief
THAN release launch codes to every local military commander.
I worked at middle-sized company that instituted a pay cuts, cutting all bonuses and stopping raises.
After year, company lost almost every person in tech managenent and most of team leaders, their clients actively executing forking rights and no one believes in company future now.
I once heard wise words from some CEO. In harsh times, clients do not want cheaper and worse services from us. They want less services. So we are moving out headcount down, while keeping pay and even execute raises for those who stay.
Intresting that this problem (IO-bound threads should have priority over CPU-bound threads) already solved at OS level (most OSes will give priority boost to thread that was unblocked because of end of IO operation in hope that thread will soon block with another operation).
No, we can provide proprietary scripts that install GPLed software (i.e. setup Linux machines), but can't provide proprietary scripts that install AGPL.
I'm a vendor of some packaged on-premise solution. We are using a Redis as a cache layer inside. Risk of being forced to GPL out our installer is unacceptable for us.
I also think that both docker-compose & k8s & helm are wrong layer of abstraction. I see a lot of people building a opinionated way to run containers and way for them to communicate with another, to request a DB or a redis.
I like to name some such attempts:
- .NET Aspire
- Avito Plato (home grown PaaS of ¨russian Amazon")
- infrastructure layer of our ZIIoT (MES platform on top of k8s)
> Maybe I’m bad at searching for these things, but these changes to C# seem to have gone completely under the radar in places where you read about memory safety and performance.
The reason is this changes are not aimed on average Joe developer writing C# microservices. This changes and whole Span/ref dialect of C# are aimed on Dr. Smartass developer writing C# high performance libraries. It's advance-level feature.