4 ms·
Writing code is one thing though. Now you have to figure out how to run a CI on a build server. Deployment on your production systems, be it containers or even
by tetha 6y ago
Writing code is one thing though.
Now you have to figure out how to run a CI on a build server. Deployment on your production systems, be it containers or even not. Monitoring, alerting, profiling, tuning under load. You have to support a new database connection library with new shenanigans. In general, you need to integrate the new language into the existing ecosystem. The latter may even be impossible depending on the stack and solution chosen. Just look up those weird Java only caching servers.
All of that is possible, sure. Due to company acquisitions and specialized teams in some areas, we're kinda running the full bingo card of languages.
But there's little denying: We overall spent less time handling language runtimes and language-specific monitoring back when we were java+mysql and that's it.
- rumanator 6y ago> Now you have to figure out how to run a CI on a build server. Deployment on your production systems, be it containers or even not. Monitoring, alerting, profiling, tuning under load. You have to support a new database connection library with new shenanigans. Most if not all of those items are either trivial or non-issues. In fact, I would argue that deploying a Python app is a far more convoluted process than getting an ASP.NET Core app up and running. With Docker, the problem simply disappears. Getting it to build and test on a CICD pipeline is as hard as typing $ dotnet build, or $ dotnet test. > All of that is possible, sure. Not only it is possible, it's laughably easy. We are supposed to avoid our problems, not perpetuate and aggravate them as eternum because we are too lazy to look for ways to make our life easier.