1. 8

    This is fantastic. Just watching the screencast is getting my creative juices flowing. What would a shell that always had this look like? We’d need some way to handle destructive commands like rm. Or commands that don’t just take time to run but also are expensive to rerun.

    1. 9

      <3 :)

      Actually, after I imagined it, I found it kinda hard to believe nobody seems to have done it earlier?… I think the pieces were mostly all there since the dawn of Unix, or before still.

      For me, Luna is the logical next step. But I got the idea before I learnt about them, and Luna is still a bit too early to be usable in this use case, so I couldn’t restrain myself to wait any longer. But I would totally love to concede to them in the long term, and I’m looking forward to a future where Luna reigns…

      As to rm… I was kinda scared after my first idea, that it would be dangerous… but then, it’s hard to accidentally type rm, and you need to give it some params anyway… So, in the end, I couldn’t think of any actual commands that would be more-than-typically risky here. That said, I have an idea for a means to protect against some simplest accidents. But, uh, I have really many ideas for up, and I really wanted to share as soon as possible, in some useful enough form… I myself find it hard to live without it at my hand’s reach, now that I know it exists.

      edit: Personally, I’m kinda stoked about one more idea I mentioned in the readme: of capturing stdout of already running processes… like if you do something, then be surprised it takes longer than expected… not wanting to kill it now and restart with a pipe… just run a capture command after the fact, maybe plug it in to up, and go on like nothing happened… :) this could be a totally separate tool. In fact, AFAIK there are already some like this, but I think they may need some refreshing…

      edit 2: as to rm… uh, oh, now I think of it, a tool is not really Unixy if you can’t potentially hurt yourself with it, amirite? ;P

      1. 7

        Actually, after I imagined it, I found it kinda hard to believe nobody seems to have done it earlier?… I think the pieces were mostly all there since the dawn of Unix, or before still.

        It was “done” before. Pipecut which seems to never have been released. The author wanted to “clean up some code first” and there you go. :( Perfection is the enemy of something or other.

        Glad someone actually finished something like this.

        1. 3

          I remember watching the video for that (with slides) thinking it was a great idea. Not sure what happened to it, but I’m glad somebody came up with the good idea and is moving forward with it.

          Note to @akavel, please go through pipecuts ideas (even if you don’t use them). One of the things I remember is that he had thought out a lot of the design, so you can figure out some of the design decisions even faster.

          1. 1

            Oh, awesome, thanks a ton! I didn’t notice the links to slides and video when glancing through their website, and your kind and thoughtful recommendation makes me really want to check them. Thanks!

          2. 1

            At this time, the author wants to clean up some portions of the code … The code will be published at code.google.com/p/pipecut

            Wow —haven’t seen a Google Code link in a while 😄

            1. 1

              Oh, interesting, thanks! I’ll add it as “prior art” in the readme then.

            2. 2

              ’m kinda stoked about one more idea I mentioned in the readme: of capturing stdout of already running processes… like if you do something, then be surprised it takes longer than expected… not wanting to kill it now and restart with a pipe… just run a capture command after the fact, maybe plug it in to up, and go on like nothing happened… :)

              https://github.com/nelhage/reptyr

              1. 2

                Yes :) Thanks! Also potentially: neercs, injcode. I just haven’t found time to research them enough yet to learn how to make them cooperate best…

          1. 2

            I’m working on Swagger UI’s Docker image - we want to expose more configuration options through environment variables, so I’m dropping the current approach of using sed in favor of a Node.js script that generates a JavaScript fragment for the image to serve up.

            1. 9

              A few times in my life, I’ve encountered a website with infinite scrolling that had a link I needed to get to in its footer. Truly awful.

              1. 3

                I’m driving to Savannah, Georgia for the week on Sunday, as well as building out helper tools for my accountability/habit-tracking-as-a-service project (https://consistency.club).

                1. 4

                  This is one of those rare pieces that are at once informative, insightful, and entertaining.

                  1. 32

                    I don’t see why this progress bar should be obnoxiously put at the top of the page. It’s cool if you wanna do a donation drive but don’t push it in the face of everybody who comes here. Honestly at first I thought this was a bar for site expense. Then I realised it’s to ‘adopt’ an emoji.

                    1. 7

                      Lobsters isn’t a daily visit for most readers, probably even for most users. They can’t see it to join in if there isn’t anything visible for it, and it has an id for adblocking if you prefer not to see it.

                      1. 22

                        Personally a check this site quite regularly on my mobile device… which doesn’t have an ad-blocker.

                        1. 13

                          That sounds awful. If you’re an android user, normal uBlock Origin works on Firefox for Android just like it does on desktop. :)

                          1. 3

                            Or use Block This!, which blocks ads in all apps.

                            1. 3

                              Oh, that’s a cool little tool. Using a local VPN to intercept DNS is a neat trick. Unfortunately doesn’t help with in this case because it blocks requests to domains and not elements on a page via CSS selectors.

                              That does make me want to actually figure out my VPN to home for my phone and setup a pi-hole, though.

                            2. 2

                              Ohh! Good to know, thanks.

                            3. 2

                              Firefox 57+ has integrated adblocker nowadays, on both desktop and mobile; plus, there’s also Brave.

                            4. 27

                              That is still annoying that I need to setup my adblocker to fix lobste.rs. So much for all the rant articles about bad UX/UI in here.

                              1. 11

                                maybe one could just add a dismiss button or sometimes like that? I don’t find it that annoying, but I guess it would be a pretty simple solution.

                                1. 1

                                  I concur, either a client side cookie or session variable.

                                  1. 1

                                    Well, yeah… that’s how you could implement it, and I guess that would be the cleanest and simplest way?

                                2. 2

                                  It’d be great to see data about that! Personally I visit daily or at least 3 times a week. Lack of clutter and noise is one of the biggest advantages of Lobsters. And specifically, I looked at the link, and I have no idea who this Unicode organization is, or their charitable performance, or even if they need the money. I’d imagine they are mostly funded by the rich tech megacorps?

                                  1. 1

                                    [citation needed] ;-)

                                  2. 3

                                    Adopting an emoji isn’t the end goal: the money goes to Unicode, which is a non-profit organization that’s very important to the Internet.

                                    1. 5

                                      If this bar actually significantly annoys you, I’m surprised you haven’t literally died from browsing the rest of the internet.

                                    1. -2

                                      you’ll be fine. harden up and keep going.

                                      1. 19

                                        FWIW, telling people in crisis to “harden up” is rarely helpful.

                                        1. 8

                                          This is not good advice.