A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community’s icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
None of those things require Docker or Kubernetes…
I don’t necessarily disagree. There are many ways to achieve the same or similar results. But docker seems to have become the popular option to the point where services are offering docker configurations out of the box. Meaning I have a standard, officially sanctioned way of doing what you described. Someone has already figured out how to properly containerize what to me is only a dependency and I can focus my efforts elsewhere. The option to get my hands dirty is still available, but it becomes a choice.
Yup, you can definitely take shortcuts that make development easier at the cost of maintenance being harder and more expensive. That’s exactly the problem I was describing.