7 ms·
Some features being absent is not the same as what you said in the article. "Any GitLab instance other than gitlab.com [..] none of these are going to work unle
by arp242 6y ago
Some features being absent is not the same as what you said in the article. "Any GitLab instance other than gitlab.com [..] none of these are going to work unless every host is added and the list is kept up-to-date manually." makes it sound like they don't work at all, but in fact it's just a few minor features that don't work. sr.ht has always worked on pkg.go.dev from day 1.
Actually, pkg.go.dev needs to have some way of figuring out where to link to, so it's not necessarily easy to automatically make links that work for 100% of the sites. That's not "a blatant failure to comprehend the fundamentally decentralized nature of git hosting", that's having to deal with a large ecosystem spread out over thousands of domains. Go's model is a lot more decentralized than most other package systems (which also makes stuff like this harder).
- ddevault 6y agoThey do have a way, and godoc.org uses it: go-source meta tags. https://news.ycombinator.com/item?id=24024130 https://news.ycombinator.com/item?id=24024130
- arp242 6y agoThat doesn't address the main meat of the comment, which said that your claims in the article are highly misleading.
- ddevault 6y agoI don't think that my claims are misleading.
- arp242 6y agoYou suggested many code hosting sites don't work, while in fact they do work except for some (IMHO minor, but we can perhaps disagree on that) features. You don't think that's not a full and accurate representation of the state of things?
- ddevault 6y ago>they do work except Except being the key word here. My commentary is on the quality of their engineering approach and I have demonstrated that their approach is flawed. Their approach is wrong.
- arp242 6y agoNone of that is relevant; you can feel the Google engineering approach is the worst in the history of humanity – all fine with me – but ..... that does not mean you get be misleading about facts. You can – and should – state that one feature doesn't work; rather than say that none of it works. Because the former is true, and the latter is not. What is the goal of your post? To inform your readership, or to convince them that Google is bad? If it's the former, then you have done your readership a great disservice. If it's the latter – which seems to be the case – then congratulations: you've fooled your readship – or at least part of it – in to believing something that's not true.
- ddevault 6y agoMy goal - my stated goal, that is - is to point out that the engineering approach is flawed. I don't have to explain the degree to which the feature is wrong in order to utilize the fact that it is wrong as a mark against the engineering approach. The approach is wrong, they were told, they didn't change it. End of story. And you've been misleading yourself: it's not a "single feature" - several features depend on this code. It is a second-class experience, and in ways that build upon other problems I've put into the article. Cut the bullshit, dude.
- akerl_ 6y agoYour post states that their approach is flawed in large part because it only works for sites which have been explicitly declared in the service’s config. Given how key that is to the case that the engineering approach is flawed, it seems very relevant that the majority of the service does work for any site, and there are specific features which require the site being included in the service config. There’s a big difference between requiring explicit site inclusion for full functionality and requiring inclusion for any functionality, and your post claims the latter.