| You forgot : - deal with management who wont pay for a support license because the product is "Open Source" - spend weeks troubleshooting dependancy hells for applications with no documentation and no architecture and listening devs tell you that "it works on their laptop" (but somehow they can't give you a working requirements.txt or equivalent) - the immense pleasure of using apt, pip, npm, and all of their cousins behind corporate proxies - deal with information security departments who have no idea what you are doing, and thus feel threatened and block all of your initiatives by default - deal with infrastructure departments who are building their own internal cloud infrastructure, with no budget (hello again free "Open Source"), and won't label it "prod-ready" after 4 or 5 years while support for their legacy is dropped - convince management that they may have to give some training to their 60 "integrators" and 80 "exploit" teams that are still copying and pasting shell scripts from Word documents written last decade or earlier |