1. 21
  1. 24

    It’s pretty, but just give me the documentation.

    1. 3

      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.

    2. 12

      This is “Superb”? https://puu.sh/IZ2xr/5b5cf8df39.png

      I’ll stick to man pages.

      1. 10

        Ah, yes, printf(3), the well-known OCaml function.

        1. 6

          “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.

          1. 6

            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!

            1. 4

              No critique, but I find it funny that the «Top 10 commands» are mostly deprecated:

              1. cron: insert comment about the scope creep of systemd
              2. traceroute: Ok, I don’t know of a better traceroute.
              3. tar: Why remember tar when atool works on any archive and is safe against tarbombs.
              4. 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/.
              5. netstat: Superseded by ss and ip.
              6. 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.
              7. 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.
              8. iptables: Superseded by nftables
              9. curl: Ok, there is wget too, but they aren’t in a particular need of replacement.
              10. 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.
              1. 5

                cron: insert comment about the scope creep of systemd

                systemd-timers provide way more functionality than crond. It’s a valid improvement, not just a simple replacement.


                mtr, tracepath

                1. 4

                  re: better traceroute, I think that’s mtr

                2. 4
                  1. 2

                    This is more to my liking, thanks

                  2. 5

                    A bit disappointing that this uses GoogleAds. Not sure what ads add to this website.

                    1. 1

                      Sorry, I have Ka-Block! and I didn’t notice any ads on the site.

                      1. 1

                        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.

                        1. 4

                          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.

                          1. 1

                            Indeed, although on these kind of sites, there isn’t any ads usually so I was surprised.

                    2. 2

                      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.

                      1. 1

                        The FreeBSD Handbook is the gold standard IMHO

                        1. 1

                          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.

                          1. 2

                            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.