Slumber a TUI HTTP Client(slumber.lucaspickering.me)
49 pointsby jicea4 hours ago12 comments
  • sgt2 minutes ago
    The "Postman" team hates this one app...
  • hunter2_an hour ago
    TUI stands for "Text User Interface" not "Terminal User Interface" considering that the point of TUI vs GUI is to distinguish text mode from graphical mode. The word "terminal" isn't really meant to imply text even if quite a few terminal emulators are, indeed, text mode; rather it typically means that the UI is drawn by some other machine than the one you're touching. For example, a very popular Windows Server feature formerly named "Terminal Services" is for GUI terminals, not TUI terminals. A likely source of confusion is the MacOS app named Terminal, which only becomes a terminal in the real sense of the word once you decide to let some other machine draw your UI (ssh, telnet, rlogin, etc.).

    But it looks very cool!

    • _fluxan hour ago
      On the other hand, there are many elements in the user interface that are not text. In fact, I think it would be quite understandable if one even separated REPLs like bash or octave to be "text user interfaces" while applications that make use of character placement and border special characters "terminal user interfaces", because they use means beyond text stream to communicate with the user. One might even render straight up graphics to a terminal [emulator application].

      Even X had a separate application called xterm 42 years ago: the complete X system was not to my knowledge called a terminal system, except perhaps when discussing the dedicated client devices, such as VT1300. Also the term "virtual terminal" as far as I know has always referred to a the kind of interface this application is making use of.

      So I think we can just accept that the term is overloaded such that "terminal" refers to both of these situations, as there is no historical precedent to have it exclude the other situation, and the term "terminal-based application" is completely clear to a rational listener.

      • nine_k44 minutes ago
        A REPL like bash already is not a pure text stream, since readline is used. Zsh, even less so.
    • dual_dingoan hour ago
      I would argue that a local only session with terminal.app is still a real terminal session because the app is just a terminal for the connection to the MacOS version of getty. In principle, this is not different from having a serial cable between the host and an old-style terminal or encapsulating that connection over a different network like with SSH and telnet etc.
  • ananthakumaran15 minutes ago
    For those who are using Emacs, https://github.com/federicotdn/verb provides similar UX, I have been using it as a postman alternative for quite some time.
  • jhy19 minutes ago
    > Slumber is a terminal-based HTTP client, built for interacting with REST and other HTTP clients

    I wonder what that means -- I looked around the docs but didn't see that it interacts with other clients. I thought maybe it would show a generated curl command or something along those lines. But perhaps it's just a typo for HTTP servers?

  • dhruv3006an hour ago
    Great to see this space so active.I see this a TUI.

    You can also try out Voiden : https://voiden.md/ which has a different approach to this.

    Also YAML is a interesting choice - any reasons for this.

    PS : I am associated with Voiden.

  • voidUpdatean hour ago
    > "To that end, configuration is defined in a YAML file called the request collection"

    Genuine question, why do people use YAML? I've been using it a little bit recently (reading existing documents, not writing my own), and it just seems like a more overcomplicated and less human-readable version of JSON? With potential security vulnerabilities?

    • mystifyingpoi26 minutes ago
      > less human-readable version of JSON

      Please provide an example, how YAML can be less readable than JSON. I struggle to think of any.

      • voidUpdate11 minutes ago
        Indentation based structure isn't really a good thing in my eyes, where the format of the document encodes semantic meaning. With JSON, you can display it how you want, and because it's bracketed it will still encode the same data.

        Also I really don't like the hyphen notation... This is very unreadable to me:

          - a
  - b: c
  - - d
    • amazingmanan hour ago
      People use YAML because a bunch of other people use YAML. Whatever its warts, there's no use resisting it.
    • kalaksi40 minutes ago
      If not using any esoteric features, it's more human readable (imo), easier to write, can have comments and has some useful features like different kind of multi-line values. JSON is valid YAML, by the way.
    • bschwindHN43 minutes ago
      > it just seems like a more overcomplicated

      Because people LOVE overcomplicated shit. You see it happen everywhere.

      • kalaksi36 minutes ago
        I don't think that's it
    • speed_spread33 minutes ago
      Because as long as you stay away from anchors and inline JSON, YAML is a perfectly workable, structured, human-readable format that supports comments.
  • vladde36 minutes ago
    looks nice when you want to quickly get something up and running! i'm trying to move away from GUI-based, and i haven't really found a nice workflow with just using curl

    https://justuse.org/curl/

  • keylean hour ago
    If it could import and export postman collections and env, you'd have a customer for life!
  • smetjan hour ago
    That looks great! Will give it a spin during my daily work. Thanks for making and sharing it.
  • zdkaster2 hours ago
    Love the support for neovim integration
  • ualloan hour ago
    https://github.com/darrenburns/posting is another TUI client.
  • PikitiDevan hour ago
    [flagged]