Especially all these newfangled "solutions" like containerization, which are primitive workarounds for the problems of an old and poorly designed operating system. Containers and virtual machines are unfortunately only prostheses, not the optimal final solution.
Yes, but it also depends on what one wants to do. Containers solve the problem of "it works on my development machine, but it doesn't work on another machine". Before using containers, I had to think of what OS (Windows/Mac/Linux) I would deploy my application onto.
Since I started using containers, I only develop on Linux, test in a local Linux container AND deploy to any OS that can run a minimal Linux OS container like Alpine Linux. This example in the Wiki
https://wiki.lazarus.freepascal.org/Docker_Containerization was a good starting point for me. It gave a new lease of life to my old Lazarus applications.
It is hard to call Object Pascal outdated when a well-designed containerized Object Pascal server on legacy machines can handle considerable loads in real-time.
Another use case is multi-tenant database applications. Running databases for different tenants on the same machine but listening on different ports is trivial with containers. One can even mix and match different versions of the same database on the same machine in different containers. Testing the latest version in its own container before deployment, while the legacy versions remain untouched. Using tools like docker-compose also means one can deploy an entire full stack web application in under 10 seconds.
Are containers for everybody? No, but once you try them, especially for server-side development and get used to it, it is hard to not appreciate the convenience they bring.