Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I love how you intentionally cropped off the first two words of that sentence, try to make out that their 30 word side note was actually the whole point of the 800 word article, and you STILL didn't manage to make them sound as malicious as you wanted to.

"give us a hint" - "Stop begging!"

As I say, you're clearly coming into this with a strong unjustifiable bias, I can tell because you're forced to use words like "smear", "parasite", "exploiting", "beg", "indentured servitude" - it's a cover for the cognitive dissonance.

But if you genuinely would like a discussion about the pitfalls of the funding models of open source, yeah it's a reasonable question that has never been satisfactorily answered. There are whole PHD projects on the subject, and nobody's cracked it. Giving money to open source projects is difficult for many reasons - ranging from tax treatment to geography even to legality. Providing services is somewhat easier, but in many companies in some countries even that comes with geopolitical legal issues. Marketplaces only work if you have something to barter, and if you would like to contribute to the freedoms you enjoyed, it's hard to make that work in a marketplace model, not to mention that even providing people the option of donating money for a product comes with overhead (legal / technological / service / financial network / server etc).

If you would like a discussion about ensuring abstractions over the services you use, sure, I'm here for it. Of course, it's hampered by a lack of consistent interfaces, and in some cases interfaces that ensure they can never be smoothed over. But that sounds like a cool open source project - in this case, I guess it would be an anyhub kind of deal that can serve images for different use cases, paired with a DSL for defining a resource (that can generate a dockerfile / docker compose file, in docker's case). Of course, serving images isn't free, but you've cracked the problem of funding models of open source, right? Right?

And you mention indentured servitude, loaded though that phrase is, it's also a poor analogy. Tax would be a closer match. You depend on open source and make money off it? Great. Giving open source a cut of that pie in some way seems the morally right thing to do. How you do that is up to you, but telling people they can use your service then pulling the rug while simultaneously ghosting them? That sounds kind.

You know what, I think you're right - it's so much easier to lambast someone for daring trust or daring to express concern than it is to do anything meaningful to improve the landscape.



> if you genuinely would like a discussion about the pitfalls of the funding models of open source

That is absolutely what I want, and I appreciate your contribution to the debate.

> you're forced to use words like "smear", "parasite"

I'm just trying to use fewer words, because people's attention spans are really short these days, which naturally requires the words to have more dense and intense meaning.

> it's so much easier to lambast someone

It's not easy, it's hard. People are refusing to accept that corporations are not your friends. Have you ever tried criticizing Apple?

My critique is specifically that the article:

1) presumes that Docker Hub should provide the service, despite clearly not responding to their application for free service.

2) then uses an article that invites peer pressure onto the company to get what they want.

Instead, I argue that it would be healthier if they:

1) explained why relying on Docker Hub is dangerous

2) what the alternatives are, and why they're not good enough

3) what needs to change, which may include consumer behavior - things that we control, because we really don't have control over Docker Hub.

> indentured servitude

By collectively perpetuating our dependence on them, we are engaged in self-enslavement.

And I think this type of article is a form of begging that our masters haven't given us enough breadcrumbs lately.


> 1) explained why relying on Docker Hub is dangerous

I mean, that's the other 770 words of the article. Except they're just giving their experience, and allowing you to come to your own decisions - because otherwise people might legitimately call them out for "smear" tactics.

> 2) what the alternatives are, and why they're not good enough

"as we grew we started mirroring our images to Gitlab and Quay.io," <= Alternatives (that they are using)

"Docker Hub is the de facto standard Docker registry, literally, if you don't specify a registry when pulling an image Docker will invisibly prepend docker.io/ to it." <= Why they're not good enough (extra config step)

> 3) what needs to change, which may include consumer behavior - things that we control, because we really don't have control over Docker Hub.

"but it does feel like we need to do something. Whatever we decide, we'll keep you informed." <= They're not there yet, but they're open and honest about it

> use fewer words, because people's attention spans are really short these days,

I can see that you have a short attention span.

> which naturally requires the words to have more dense and intense meaning

You are a belligerent, self important ignoramus who incorrectly believes the world needs his opinion. <= genuinely, do you like this style of discourse? Why are you treating shock language as a status quo worth maintaining, but trust and expecting decency from a corporation as some kind of unacceptable failing?


Do I like being called a "self important ignoramus"?

No.

Does it make me belligerent?

Yes.

I care deeply about humanity, and I'm surprised to conclude that we will definitely have a civil war soon.

See you on the other side.


> If you would like a discussion about ensuring abstractions over the services you use

Yes, please.

I'd love to hear your ideas, and I agree that we still need to figure things out, particularly how to make open source self-sustaining.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: