4 ms·

This is really a question of framing. The other way you can look at it is: Docker has benefitted from a community adopting its products, and developing software

This is really a question of framing. The other way you can look at it is: Docker has benefitted from a community adopting its products, and developing software that makes Docker more useful. As someone who sells Docker services, you benefit from a greater market size. It's like how WordPress have benefitted from people authoring plugins – even though wordpress.org has hosted them for "free", this has been good commercial sense as it allows them to sell more WordPress.com to people.

concerndc1tizen 2y ago
And once those services are fully developed, and the market is captured, do they still need to provide free services? Isn't compatibility issues a major problem for alternative registries?
- yjftsjthsd-h 2y ago
  > Isn't compatibility issues a major problem for alternative registries? Er, is it? I've used a handful of different registries and never hit anything that even resembled a compatibility problem. Have I just been lucky?
  - aspenmayer 2y ago
    One example that springs to mind is Homebrew/MacPorts. I think they install things differently and might not be interoperable?
    - yjftsjthsd-h 2y ago
      They do things differently, but what does that have to do with docker registries?
      - aspenmayer 2y ago
        It’s an example of incompatibility in registries generally, which I thought was the nature of your surprise at its existence or occurrence. I’m not aware of any such incompatibilities among Docker registries, but other issues may affect usage such as rate limits. I’m not sure what the person you were responding to had in mind.
  - pas 2y ago
    I had waaay too much problem with pushing to GCR, when pushing to a self-hosted GitLab's registry worked.
TZubiri 2y ago
"Docker has benefitted from a community adopting its products," It takes a whole lot of mental gymnastics to argue that a provider of free services is actually the one benefitting from that interaction, and not the other way around. Go ahead and build your systems on free dependencies like WordPress and Debian, but just get real and don't pretend that you are better than professionals that build business relationships and actually pay for their software dependencies like RHEL and Webflow.
- saagarjha 2y ago
  I mean, paying for your software dependencies doesn’t automatically make things any better.
  - TZubiri 2y ago
    It's wild that "people should pay for software" is a controversial statement amongst software developers. If software developer, don't pay for the software you rely on. Then non technical users who appreciate software even less would pay for software with much less frequency and for much lower prices when they do! It is us as developers that need to first institutionalize the idea that software is paid, otherwise we have little hope to get paid for our efforts.
    - Joker_vD 2y ago
      There is difference between paying for software and paying for the development of software, you know.
      - TZubiri 2y ago
        Yeah sure, but there's trickle down effects. What incentive would an employer have to hire you to build software, if they can't then go and sell the software that you built for profit.
        Joker_vD 2y ago
kristianc 2y ago
> It's like how WordPress have benefitted from people authoring plugins – even though wordpress.org has hosted them for "free", this has been good commercial sense as it allows them to sell more WordPress.com to people. With seemingly similar rent-seeking behaviour when Automattic decide they’ve had enough and want to put a toll on that road…
deleted 2y ago
[deleted]
keybored 2y ago
With your framing this looks like the free/“free” initial use of such a framing is similar to free accounts on new social media platforms. In that case the motivation is super clear: grow the social platform since a social platform with few users is useless. Then when they get big enough they start charging. Once you’re already locked in via all sorts of connections. Again in the case of social platforms: for the longest time this was framed as user entitlement if anyone didn’t like it. Which failed to see the other side. Yes, the users wanted something free but the company also got something back from the user. We could go back and forth on details like the service growing to such a point that the free service becomes too much of a burden on them. But consider the case when the free service was treated by the business as an investment for $X which was supposed to carry that cost until the proverbial rug could be pulled from the users without a mass exodus—grow your user base until you have enough of a mass to demand a considerable escape velocity in order to be avoided. Again, arguments could be made either way. But it is definitely not as simple-cut as an altruistic service versus selfish users/consumers. I’m sure someone versed in Economics could summarize the above in a phrase or a sentence.

concerndc1tizen 2y ago

And once those services are fully developed, and the market is captured, do they still need to provide free services? Isn't compatibility issues a major problem for alternative registries?

yjftsjthsd-h 2y ago
> Isn't compatibility issues a major problem for alternative registries? Er, is it? I've used a handful of different registries and never hit anything that even resembled a compatibility problem. Have I just been lucky?
- aspenmayer 2y ago
  One example that springs to mind is Homebrew/MacPorts. I think they install things differently and might not be interoperable?
  - yjftsjthsd-h 2y ago
    They do things differently, but what does that have to do with docker registries?
    - aspenmayer 2y ago
      It’s an example of incompatibility in registries generally, which I thought was the nature of your surprise at its existence or occurrence. I’m not aware of any such incompatibilities among Docker registries, but other issues may affect usage such as rate limits. I’m not sure what the person you were responding to had in mind.
- pas 2y ago
  I had waaay too much problem with pushing to GCR, when pushing to a self-hosted GitLab's registry worked.

TZubiri 2y ago

"Docker has benefitted from a community adopting its products," It takes a whole lot of mental gymnastics to argue that a provider of free services is actually the one benefitting from that interaction, and not the other way around. Go ahead and build your systems on free dependencies like WordPress and Debian, but just get real and don't pretend that you are better than professionals that build business relationships and actually pay for their software dependencies like RHEL and Webflow.

saagarjha 2y ago
I mean, paying for your software dependencies doesn’t automatically make things any better.
- TZubiri 2y ago
  It's wild that "people should pay for software" is a controversial statement amongst software developers. If software developer, don't pay for the software you rely on. Then non technical users who appreciate software even less would pay for software with much less frequency and for much lower prices when they do! It is us as developers that need to first institutionalize the idea that software is paid, otherwise we have little hope to get paid for our efforts.
  - Joker_vD 2y ago
    There is difference between paying for software and paying for the development of software, you know.
    - TZubiri 2y ago
      Yeah sure, but there's trickle down effects. What incentive would an employer have to hire you to build software, if they can't then go and sell the software that you built for profit.
      - Joker_vD 2y ago

kristianc 2y ago

> It's like how WordPress have benefitted from people authoring plugins – even though wordpress.org has hosted them for "free", this has been good commercial sense as it allows them to sell more WordPress.com to people. With seemingly similar rent-seeking behaviour when Automattic decide they’ve had enough and want to put a toll on that road…

deleted 2y ago

[deleted]

keybored 2y ago

With your framing this looks like the free/“free” initial use of such a framing is similar to free accounts on new social media platforms. In that case the motivation is super clear: grow the social platform since a social platform with few users is useless. Then when they get big enough they start charging. Once you’re already locked in via all sorts of connections. Again in the case of social platforms: for the longest time this was framed as user entitlement if anyone didn’t like it. Which failed to see the other side. Yes, the users wanted something free but the company also got something back from the user. We could go back and forth on details like the service growing to such a point that the free service becomes too much of a burden on them. But consider the case when the free service was treated by the business as an investment for $X which was supposed to carry that cost until the proverbial rug could be pulled from the users without a mass exodus—grow your user base until you have enough of a mass to demand a considerable escape velocity in order to be avoided. Again, arguments could be made either way. But it is definitely not as simple-cut as an altruistic service versus selfish users/consumers. I’m sure someone versed in Economics could summarize the above in a phrase or a sentence.