Threads for nj47

  1. 10

    A question we’ve all been wondering, which unfortunately went unanswered:

    What’s it take to get the display software certified? It’s an electron application, right? Most people in aerospace that I know would balk at the idea of allowing a garbage collected runtime in something like a real time aircraft display, let alone bundling a full browser into the application. What’s the difference here? Is a display in a rocket not necessary for crew safety in lieu of some other backup? – /u/JameslsaacNeutron

    1. 8

      The astronauts are cargo and aren’t required for flight - Dragons have autonomously resupplied the ISS many times - so the screens and their associated stuff are not in the loop in any meaningful sense. This has been a tension in the astronaut corps since the earliest days of spaceflight (Yeager famously described astronauts as “Spam in a can”).

      Where astronauts are actually pilots (not technologically necessary but via political victory, such as with the Space Shuttle) the interface is completely different - no touch screens to be seen (and yes they were an option even back then) because they’re extremely unwise for safety-critical controls and interfaces. The level of autonomy in the dragon means that most mental models we have about ‘pilots’ ‘flying’ the spaceship are not relevant, and the displays are a retrofit on top of the existing hardware and are not deeply embedded into the control system. Much like your HTML monitoring dashboard for your server farm.

      Mission control on the ground is as much in the loop as the astronauts, and better placed to deal with most issues that would arise that you might thinking would be an occasion for astronauts to do manual interventions. And all that is quite well debugged by now.

      Source: friends on the inside.

      1. 1

        Did you ever read about this disaster? If you didn’t have friends on the inside, I would say your post is likely accurate based solely on the linked story. Touch Screens are awful interfaces if you actually want people in control.

      2. 5

        I cannot imagine it is certified as safe software. So it must be properly isolated and unnecessary. Isolation is easy. Unnecessary in terms of input comes from the fact that there are also physical buttons. What is left open for me is the output: How can you be confident that the information shown to the astronauts is correct with a big block of unsafe software in between? Is there redundancy somewhere?

        1. 1

          In addition to what balloonatic said about the astronauts being more like cargo these days, I suspect this is a key piece of the answer as well.

          You’ll also notice in certain images too that there still exist some hardware buttons in the capsule right below the displays; this is also ensure that in case the displays are unusable for whatever reason, the astronauts can still use hardware buttons to initiate critical actions, such as responding to a fire in the cabin. - Wendy

        1. 7

          Alfred, iTerm

          I can never get a concrete reason why to use these over Spotlight/ There used to be a significant difference, but today I can’t think of a compelling reason.

          Edit: Ditto for flu.x

          1. 4

            Personally, I couldn’t let go of having shortcuts to switch to the nth tab. Thus, iTerm beat Terminal for me.

            1. 3

              I use Alfred primarily for various workflows that I have set up. That’s not something that can replicated with spotlight.


              I have a few smaller ones that I’ve designed myself.

              I use the Github Repos Workflow constantly:

              1. 2

                I happily used Spotlight for years. Then, a couple OSX updates back, it stopped properly indexing applications. I never was able to fully figure out what the problem was, as there was seemingly no pattern to which applications would be excluded. At one point it stopped including Chrome in the index, and that was the straw that broke the camel’s back for me. (More specifically, I believe it still included them in the index based on testing the command line interface, but Spotlight simply stopped showing them.)

                I switched to Alfred, and it immediately worked “perfectly” - which is to say it performed identically to how Spotlight did before the updates. It’s been a few months now, and I have no complaints with Alfred, it does everything Spotlight did, and is much faster.

                1. 1

                  Weird! In your position I think I would have done the same thing.

                  1. 1

                    I have the same problem and switched to Alfred for the same reason.

                  2. 1

                    iTerm is waaaaaaaay ahead of

                    1. 6

                      I keep getting replies like this, but still no concrete reason.

                      1. 8

                        I think it’s because there aren’t great reasons anymore. Yes, you’ve got some tmux integration and similar I guess, but e.g. tmux support requires (or at least used to require) custom-built versions of tmux that kept it from being as useful in practice as you might think. Meanwhile, Terminal itself has added tons of features that used to be iTerm-only and added some of its own (e.g. window groups), and while there’s some comments below that iTerm has smoother scroll, I have noticed that using Terminal can actually speed up programs I run if I’ve got them dumping directly to stdout (because it can get stuff on the screen faster).

                        I used iTerm for many years, but I’m also back to Terminal. Ditto for Alfred, similar reasons.

                        1. 6

                 has added

                          • Mouse Reporting
                          • Ligatures (which is still in beta for iterm)
                          • Vertical and horizontal character spacing
                          • Key macros
                          • Tabs
                          • Window groups
                          • Custom entry commands
                          • STDout Search.

                          The difference between iTerm and is becoming more superficial. At this point the largest difference is the degree of customization, and people who care about this seem to be more evangelical about it.

                          That being said I still use iTerm for two reasons.

                          1. Hotkey Quake like drop down terminal window.
                          2. Its what I’ve been using.
                          1. 1

                            Only things missing from are:

                            • True Color support
                            • Hotkey dropdown
                        2. 7

                          smoother scroll, true color support, greater tmux integration, splits.

                          On the other hand I think has the edge with better font rendering and slightly smoother performance (latest Beta version of iTerm2 is much much better in that regard, but has still edge on that front, but it’s locked on 30fps, so it’s not that much greater in the end).

                          1. 5

                            Btw I’m still using because I found it much more stable, and I’ve stopped using tmux for terminal splitting and tiling. Now I use Tmux mostly for attaching and detaching and security reasons, as tmux increases input latency which I cannot stand!

                            And most important of all is that I didn’t want to become addicted/attached to my personal dev environment. I have been through customization hell with Emacs and Vim, now I am back to really minimal 200 Loc configs in both, using mostly stock stuff on macOS, and some universal UNIX programs. I have around 10 applications installed on my macOS, rest is stock Apple stuff and it works really well!

                            1. 2

                              What phl said :-) also, better splitting. Better full screen mode.

                            2. 1

                              I recently tried switching back to, but couldn’t get the colour schemes to show correctly. Terminal does something to the colours to add more contrast, and I couldn’t figure out how to fix it.

                          2. 1

                            To be fair to flu.x, that’s a relatively recent addition, and still allows a lot more control (at least on macOS) over the timing, degree, and transition curve to red-shifted light. The rest, I’m with you.

                            1. 2

                              To be even fairer, it’s “f.lux”, not “flu.x” ;)