News for hackers. Stuff that matters.
Re:Docker Expands Relationship with Microsoft by donmcronald on Thursday May 28, 2020 @12:20PM (#23339085)
> The idea of the integration is to make it easier, faster and more efficient to include Docker containers when developing applications with the Microsoft tool set. Docker CEO Scott Johnston says it’s a matter of giving developers a better experience.

What they actually mean is the opposite. They want to make Azure the easy choice when developing with Docker. They go on to say it can take hours or days to get the integration set up manually.

If Azure “just works” and the other clouds take days to get integrated, owning Docker would let them make Azure integration a priority while neglecting or sabotaging integration to other clouds. The gap gets bigger and Azure feels even more like the obvious choice if you want to get anything done.

IMO one of the major cloud vendors will buy Docker this year. Microsoft seems like the obvious choice right now.

Re:Docker Expands Relationship with Microsoft by cosmie on Thursday May 28, 2020 @12:35PM (#23339295)
> If Azure “just works” and the other clouds take days to get integrated, owning Docker would let them make Azure integration a priority while neglecting or sabotaging integration to other clouds. The gap gets bigger and Azure feels even more like the obvious choice if you want to get anything done.

Which is a playbook they've demonstrated as recently as last October, on Mover[1]. It used to allow you to migrate data between a whole host of sources and destinations, and the guides/help docs even still reference those capabilities. Microsoft acquired it and made it free, but have turned it into a one-way tool: the only supported destinations are now Azure, Sharepoint, and OneDrive.

[1] https://mover.io/

Re:Docker Expands Relationship with Microsoft by revel on Thursday May 28, 2020 @01:39PM (#23340113)
Totally agree with you. This is an attempt to make heroku for enterprise-scale systems. The risk, as a user, is that you end up locked into a ton of automatically configured, Azure-specific costs. It's a recipe for an anti-trust suit based on bundling (ie. the same situation that MS lost with IE many years ago).