3 ms·

Well some say 'all publicity is good publicity', I think in this case it has hurt MinIO more than anything as far as public adoption is concerned.

reconnecting 1y ago
I believe it's too early to judge public adoption. Let's see in a few years if it degrades somehow. For now, they jumped from 55,880 to 56,319 GitHub stars in one day. From the product side, I don't see how this should affect new adopters who didn't read the hn post yesterday
- elAhmo 1y ago
  GitHub stars are useless metric.
  - msarrel 1y ago
    Almost as useless as docker pulls, and MinIO claims both as vanity metrics.
    - reconnecting 1y ago
      OK, have a look at GitHub contributors metric. 404 today, 405 yesterday. Just to clarify, I'm not affiliated with or protecting MinIO, I don't know anything about this software. But it seems to me that there's some overreaction about Docker here, and in reality it is highly possible that this decision might not affect the product the way it's being discussed these days.
      - NewJazz 1y ago
        Are those active contributors or lifetime contributors? And don't those counts leave out anyone who doesn't have a github account or doesn't associate their got email with their github account?
        reconnecting 1y ago
        I'm not sure that GitHub provides those metrics, unfortunately.
        NewJazz 1y ago
        Baffling considering how much they charge and how easy it is to get that info just from the git repo data.
  - reconnecting 1y ago
    If stars are useless here, I see that only one contributor is left after all that happened yesterday (505 to 504). It's not changing the fact that it's too premature to reflect on public adoption at this moment.
- aerostable_slug 1y ago
  Pure anecdata: the fact that this is happening at all has us (at work) looking for alternatives. Once we finalize on the best one we'll swap out MinIO permanently. I can't imagine we're the only ones, but who knows?
  - reconnecting 1y ago
    If you use this tech, perhaps you could explain what the real issue is behind dropping Docker? I mean, it's still AGPL licensed — why can't you use it from source? In other words, what is the significant difference for your team that's worth changing the stack and navigating through the uncertainty of an alternative product?
    - trueismywork 1y ago
      Ease of setup and certified working solution. And yes, people should pay for certified working solution. But not when they use it the first time itself
      - reconnecting 1y ago
        Yes, I understand that Docker is easy to set up. However, I also understand that for any organization it is very painful to change their existing stack, thus I'm trying to understand what is gained between AGPL sources without Docker and switching technology to something different with Docker except 'ease of setup'.
        trueismywork 1y ago
        A lot of small shops will find it easier to shift to a compatible S3 object storage which have their own docker compse scripts up and running than figure out how to build minio images successfully. Most products nowadays gives you ansible and docker scripts which can get you up and running inside an hour and then you can configure stuff later. Building something on your own on the other hand is probably easily a half-time engineer just for build quality and dependency tracking. Huge number of MinIO shops is one head node and 7 jbods in a single rack (giving you more thsn 10PB). And two such racks for redundancy and one offside rack for backup.

reconnecting 1y ago

I believe it's too early to judge public adoption. Let's see in a few years if it degrades somehow. For now, they jumped from 55,880 to 56,319 GitHub stars in one day. From the product side, I don't see how this should affect new adopters who didn't read the hn post yesterday

elAhmo 1y ago
GitHub stars are useless metric.
- msarrel 1y ago
  Almost as useless as docker pulls, and MinIO claims both as vanity metrics.
  - reconnecting 1y ago
    OK, have a look at GitHub contributors metric. 404 today, 405 yesterday. Just to clarify, I'm not affiliated with or protecting MinIO, I don't know anything about this software. But it seems to me that there's some overreaction about Docker here, and in reality it is highly possible that this decision might not affect the product the way it's being discussed these days.
    - NewJazz 1y ago
      Are those active contributors or lifetime contributors? And don't those counts leave out anyone who doesn't have a github account or doesn't associate their got email with their github account?
      - reconnecting 1y ago
        I'm not sure that GitHub provides those metrics, unfortunately.
        NewJazz 1y ago
        Baffling considering how much they charge and how easy it is to get that info just from the git repo data.
- reconnecting 1y ago
  If stars are useless here, I see that only one contributor is left after all that happened yesterday (505 to 504). It's not changing the fact that it's too premature to reflect on public adoption at this moment.
aerostable_slug 1y ago
Pure anecdata: the fact that this is happening at all has us (at work) looking for alternatives. Once we finalize on the best one we'll swap out MinIO permanently. I can't imagine we're the only ones, but who knows?
- reconnecting 1y ago
  If you use this tech, perhaps you could explain what the real issue is behind dropping Docker? I mean, it's still AGPL licensed — why can't you use it from source? In other words, what is the significant difference for your team that's worth changing the stack and navigating through the uncertainty of an alternative product?
  - trueismywork 1y ago
    Ease of setup and certified working solution. And yes, people should pay for certified working solution. But not when they use it the first time itself
    - reconnecting 1y ago
      Yes, I understand that Docker is easy to set up. However, I also understand that for any organization it is very painful to change their existing stack, thus I'm trying to understand what is gained between AGPL sources without Docker and switching technology to something different with Docker except 'ease of setup'.
      - trueismywork 1y ago
        A lot of small shops will find it easier to shift to a compatible S3 object storage which have their own docker compse scripts up and running than figure out how to build minio images successfully. Most products nowadays gives you ansible and docker scripts which can get you up and running inside an hour and then you can configure stuff later. Building something on your own on the other hand is probably easily a half-time engineer just for build quality and dependency tracking. Huge number of MinIO shops is one head node and 7 jbods in a single rack (giving you more thsn 10PB). And two such racks for redundancy and one offside rack for backup.