4 ms·

I'm also a lazy person! Which is why tools like this are a PITA to me. The one exception is Docker. It's not a regular part of my workflow, because of how it

by loxias 5y ago

I'm also a lazy person! Which is why tools like this are a PITA to me. The one exception is Docker. It's not a regular part of my workflow, because of how it makes things both harder to get started (making a working Dockerfile takes a bit of time), harder to debug, and slower to build (I just changed one line! Now I have to rebuild the whole image to see if it fixed the problem... &c). However, for deployment of the final product? I agree Docker's GREAT. But, consider, in that respect it offers nothing I didn't have at the start of my career 20 years ago. Static linking for interpreted languages. :)

thrashh 5y ago
Remember that Docker does cache intermediary builds (each Dockerfile line being a build) so when you are developing, avoid editing any existing lines and then combine it back together when you get it working. Deployment of Docker is gross, but I think that’s because that space IMO is very immature. From my experience, when something has a poor interface (Backbone.js, AngularJS, UMD, etc.) I avoid learning it because I know something is going to replace it. Kubernetes is currently squarely in that boat as far as I am concerned.