1. 3

    It doesn’t. Isn’t tab presentational? Like the way you may style the beginning of a paragraph? That’s all part of the style given by CSS. For tabular data on the other hand you have tables, and PRE for pre-formatted text.

    1. 3

      I think they mean tabs as in layout/windowing, not spaces.

      1. 3

        I was confused too. First I thought of tabs, as in \x09, the thing that shouldn’t be used when indenting source code. Then I thought of things that can be reached and navigated through when the TAB key is pressed, i.e., using tabindex, but finally realized this is about tabs to switch between windows (as in tabbed browsing)

      1. 2

        then uses UDT (a reliable protocol from the 2000s) instead of TCP (a reliable protocol from the 1970s).

        It’s the first time I come across age in a comparison of UDT vs TCP. In any case it’s more like 1980 vs. 1974, no?

        1. 4
          1. 6

            Oops, there goes my first comment in lobste.rs… Thanks for the clarification; I was thinking of UDP… and didn’t know about UDT!

            1. 2

              Welcome aboard! Have a seat. If you see a blue lobster, please give it to me, thank you.

              1. 1

                Hey, don’t feel bad…your comment got some useful replies. :)

            2. 2

              If you like UDT, check this application out:

              http://sector.sourceforge.net/

              Really shows what it can do given how they use it. :)

            1. 1

              Mosh seems like such a cool idea, but whenever I’ve ever used it, I’ve not found it any more tolerant of disconnects or laptop sleeps than ssh is. I end up using tmux anyway, so, what’s the point?

              1. 5

                I’ve found mosh to be incredibly resilient, myself. I don’t think the point is to replace tmux. For example, every time I closed my laptop I’d lose my network and/or VPN connection and have to ssh / tmux attach again. With mosh I never needed to reconnect, ever. Even when I went home or whatever and found myself on a different network.

                1. 2

                  Lots of people feel this way. Personally, I feel mosh is great, precisely used together with tmux or screen. It can disconnect for a few moments, sure, but it comes back by itself, unlike ssh. Also, ssh freezes the screen when the connection is bad, while mosh lets you keep writing. To me the fact that the connection is left running in the background is very convenient. I guess I don’t see any downsides, especially if you get scrolling through tmux, screen or similar.

                  1. 2

                    I sometimes have a few problems with a stale tmux session ending up causing visual hangs on the other clients.

                  2. 2

                    That’s the complete opposite to my experience. I’ve had a mosh session open now across VPN reconnects, through different sides of the country, in airplanes… and I just checked, for just over 40 days. How were you using it? How would it disconnect? Maybe your use case is different. I use mosh to connect to the server that I run screen on.

                    1. 2

                      It’s the opposite for me. It feels like a rather horific idea – it handles terminal drawing for me, breaks scrolling, is an ad-hoc screen syncing protocol, has hacks like guessing at what typing should do client side, and generally feels like it’s doing way too much.

                      But it handles disconnects well, so I tolerate it for certain things. Although I keep finding myself considering going back to screen + ssh again. I really wish for something that handled disconnects as well, but didn’t do all the other junk. But I haven’t been bothered enough to write something like that yet.