So, basically, MinIO is dead. Time to move on, folks. Dead horse is dead. Kicking it will release toxic decomposition sludge.
How times changed.
431–440 of 585 posts
So, basically, MinIO is dead. Time to move on, folks. Dead horse is dead. Kicking it will release toxic decomposition sludge.
How times changed.
So, basically, MinIO is dead. Time to move on, folks. Dead horse is dead. Kicking it will release toxic decomposition sludge.
[flagged]
Best to get insecure and vulnerable software out of the hands of those who may not be familiar with this CVE or their change in policy that has not gotten a press release in any way.
> nice
> We’ve stopped distributing our software for free
> How dare you!
> We’ve started distributing our software for free > nice > We’ve stopped distributing our software for free > How dare you!
Earlier quoted context omitted.
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.
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
Earlier quoted context omitted.
With 100PB clusters being built and not a cent going to them, you can see why minio has gone this route. I wonder if they will be "valkeyed"? Not by AWS presumably.
That's a strange mindset, IMO. I'd be pissed if I had to pay $0.10 every time I turned a rachet, and it's weird to expect companies to have usage-based monetization on the tools they've made for others.
Software on the other hand does not naturally wear out, in the same way physical objects do.
Maintaining docker builds isn’t that huge of a burden (and likely very useful for them too), and they’re delegating hosting to a third party… I don’t get what they’re trying to achieve here.