It is interesting to see how the title effect number of upvotes and comments. I’ve submitted this other day and it did not get any upvotes. My submission: https://news.ycombinator.com/item?id=17471476
Unified access to the best community-driven cheat sheets repositories
51–60 of 87 posts
Re: Unified access to the best community-driven cheat sheets repositories
#52Re: Unified access to the best community-driven cheat sheets repositories
#53It is interesting to see how the title effect number of upvotes and comments. I’ve submitted this other day and it did not get any upvotes. My submission: https://news.ycombinator.com/item?id=17471476
Re: Unified access to the best community-driven cheat sheets repositories
#54Instead of investing in out of band resources like this, I really wish people would just contribute improvements to the upstream documentation, which is usually more comprehensive and up-to-date than any of these resources can be.
Re: Unified access to the best community-driven cheat sheets repositories
#55Re: Unified access to the best community-driven cheat sheets repositories
#56This is not working at all for me. I keep getting HTML & CSS vomit regardless on whether I use their command line tool or curl.
Try changing it to the curl user agent:
curl -A "curl/7.37.0" cht.shRe: Unified access to the best community-driven cheat sheets repositories
#57Not very respectful of https://github.com/chrisallenlane/cheat to use the same name. The original cheat does exactly the same thing, has a big following and more stars, and has existed for years. I've opened an issue re: the name conflict https://github.com/chubin/cheat.sh/issues/34 Afaik these are the big players in the space: - bro: https://github.com/hubsmoke/bro - tldr: https://github.com/tldr-pages/tldr - cheat:…
1. Our project is called cheat.sh and not cheat (for example xterm.js and xterm are two separated projects and xterm existed for decades before xterm.js; should they be renamed too from your point of view?);
2. We are trying to mitigate the impact by using cht.sh where possible;
3. We do not and did not ever use the name to steal, to borrow, or to somehow use popularity of cheat.
I do not see any naming conflict actually. The client/command is called cht.sh, does not even have cheat in their name.
I am a big fan of the cheat project myself, and I don't want to do any harm for it. Even more, as I said, I would prefer that we cooperate with that project.
Re: Unified access to the best community-driven cheat sheets repositories
#58Re: Unified access to the best community-driven cheat sheets repositories
#59It does beg the question when do the curl versions get updated?