Instead it's owned by an abrasive difficult to deal with developer who will argue "you're just doing it wrong" with paying customers. Clearly things aren't exactly roses and sunshine here either.
Idk, I don't have the source for the conversation, but I suspect "direct" is being misinterpreted as "rude".
Using git and mercurial for large binary file storage is, 100%, wrong. Why? They're not designed for it, so they handle it really poorly. Hacks like Git LFS and annex were made for a reason.
From sourcehuts perspective, they need to serve all their customers, and an extreme performance outlier for a still small platform could degrade the experience for others by becoming a significant part of the server load. Thus, it's fair to say no.
You don't think it's strange for a service provider to tell people that "mercurial isn't suitable for this" (even though it clearly works, and has been working for many years) and "you're writing your program wrong"?
It's fine to not support certain use cases because it's too much effort or otherwise too expensive. It's not fine to, as a service provider, tell people that their programs are (and I quote) "wrong".
If you're okay with that then that's your choice, but for me it really turned me off sourcehut.
> You don't think it's strange for a service provider to tell people that "mercurial isn't suitable for this" (even though it clearly works, and has been working for many years) and "you're writing your program wrong"?
No, not really, if done politely. Which seems to be the case here.
It also might "work" to use a large crystal vase as a hammer, but it's still "doing it wrong".
If anything, I'd fault sr.ht for having too vague usage policies and then telling users they are in violation of said policies. That's not good. But they are in alpha, so hopefully it's something that'll improve.
Using git and mercurial for large binary file storage is, 100%, wrong. Why? They're not designed for it, so they handle it really poorly. Hacks like Git LFS and annex were made for a reason.
From sourcehuts perspective, they need to serve all their customers, and an extreme performance outlier for a still small platform could degrade the experience for others by becoming a significant part of the server load. Thus, it's fair to say no.
Just like Github did back in the day to CocoaPod: https://news.ycombinator.com/item?id=11245652. They also got very unhappy.