No critique, but I find it funny that the «Top 10 commands» are mostly deprecated:
cron: insert comment about the scope creep of systemd
traceroute: Ok, I don’t know of a better traceroute.
tar: Why remember tar when atool works on any archive and is safe against tarbombs.
crontab: You don’t want to edit a distro-provided config file. For most purposes, it suffices to drop a script in a directory like /etc/cron.daily/.
netstat: Superseded by ss and ip.
cp: Rsync is in many ways a better cp. Wanna sync two directories? Unlike if you try this with cp, rsync -r work/ backup/ will do the same irrespective of whether backup/ exists yet.
ls: Its date format is wrong. For locales where the day is supposed to come before the month, it makes you read the filesize as the day number – what you read as «0th of may» (in English) means that the file is empty. Exa gets it right.
iptables: Superseded by nftables
curl: Ok, there is wget too, but they aren’t in a particular need of replacement.
chmod: Ok, not exactly a swiss knife, but it does its one syscall right. Access control lists and mandatory access control is not replacing it any time soon.
Well I didn’t either, I looked at the JS loaded to show these pages (with umatrix) and saw that googleads was included. :)
I can understand the usage of some kind of tracking to improve the website (which it might be used for), but not sure overall of the point of googleAds here.
The proliferation of browser-based docs is interesting to me, because it suggests there’s a critical mass of people who flip back and forth between their editors and a browser all the time while they program. Is this a web dev thing? It’s hard for me to imagine using docs that aren’t integrated into my editor.
I do this, but that’s partially since my editor is vim, so unless I’m looking for vim documentation, I need to look it up elsewhere. For man pages and (where available) C library APIs I just use good-old man(1), but for most library reference docs I reach for the browser. I am not primarily doing web development.
It’s pretty, but just give me the documentation.
And some keyboard shortcuts, please.
I have to say I really like the looks of it, and the examples are nice as well. But a wider selection of manpages would be nice.
This is “Superb”? https://puu.sh/IZ2xr/5b5cf8df39.png
I’ll stick to man pages.
Ah, yes,
printf(3), the well-known OCaml function.“Beautiful” is too subjective. Lots of screen space is being wasted on this site. After visiting a few pages I know that it’s definitely not for me.
Superb presentation yes, but disappointingly limited selection of man pages.
It would be lovely to see this fleshed out with a larger repository of data, then combined with features from explainshell!
No critique, but I find it funny that the «Top 10 commands» are mostly deprecated:
cron: insert comment about the scope creep of systemdtraceroute: Ok, I don’t know of a better traceroute.tar: Why remember tar when atool works on any archive and is safe against tarbombs.crontab: You don’t want to edit a distro-provided config file. For most purposes, it suffices to drop a script in a directory like/etc/cron.daily/.netstat: Superseded byssandip.cp: Rsync is in many ways a better cp. Wanna sync two directories? Unlike if you try this with cp,rsync -r work/ backup/will do the same irrespective of whether backup/ exists yet.ls: Its date format is wrong. For locales where the day is supposed to come before the month, it makes you read the filesize as the day number – what you read as «0th of may» (in English) means that the file is empty. Exa gets it right.iptables: Superseded by nftablescurl: Ok, there iswgettoo, but they aren’t in a particular need of replacement.chmod: Ok, not exactly a swiss knife, but it does its one syscall right. Access control lists and mandatory access control is not replacing it any time soon.systemd-timers provide way more functionality than crond. It’s a valid improvement, not just a simple replacement.
mtr, tracepath
re: better traceroute, I think that’s
mtrSee also: https://www.mankier.com/
This is more to my liking, thanks
A bit disappointing that this uses GoogleAds. Not sure what ads add to this website.
Sorry, I have Ka-Block! and I didn’t notice any ads on the site.
Well I didn’t either, I looked at the JS loaded to show these pages (with umatrix) and saw that googleads was included. :) I can understand the usage of some kind of tracking to improve the website (which it might be used for), but not sure overall of the point of googleAds here.
It’s similar to the point of ads on most pages: the people who publish the page are hoping to make some money.
Indeed, although on these kind of sites, there isn’t any ads usually so I was surprised.
Is anyone else getting a rendering error where if you look at a man page (e.g., tar) there’s a menu on the left that covers most of the text?
I thought it was because I browse with JavaScript off, but I tried reloading with JavaScript on and I get the same problem.
The FreeBSD Handbook is the gold standard IMHO
The proliferation of browser-based docs is interesting to me, because it suggests there’s a critical mass of people who flip back and forth between their editors and a browser all the time while they program. Is this a web dev thing? It’s hard for me to imagine using docs that aren’t integrated into my editor.
I do this, but that’s partially since my editor is vim, so unless I’m looking for vim documentation, I need to look it up elsewhere. For man pages and (where available) C library APIs I just use good-old
man(1), but for most library reference docs I reach for the browser. I am not primarily doing web development.