‹ BackHN Continuity

Thread

A brief history of the Bloomberg terminal

395 points · 171 comments · rbanffy

  1. rbanffy · · focus · HN ↗
    I have the highest regard for these terse, but information-dense displays that enable humans to quickly grasp all information they need to do their jobs, and nothing more. This is also something avionics provide - a modern cockpit displays are a work of art in layering needed information for what is happening at the time, both the dense PFD and the much specific that communicate aircraft status.
    1. rubyn00bie · · focus · HN ↗
      Yeah, I think this is something a lot folks miss when doing UI/UX these days. There’s an immense focus on new users, not on folks who rely on it day in and day out for actual work. I’ve seen loads of old, incredibly “ugly” UIs that absolutely mog newer friendlier attempts at the same. They’re absolutely intimidating to new users, but once folks learn it they’re indispensable and obviously intentional.

      I really wish there was a resurgence of information dense UIs and tools, optimizing for people who use them daily and not “use it once.” It really reminds me of the hate folks have for things like Eclipse or IntelliJ which are daunting at first but once you get over the shock and learn them really are amazing tools.

      1. mandevil · · focus · HN ↗
        <a href="https:&#x2F;&#x2F;x.com&#x2F;scottew&#x2F;status&#x2F;1751357591375208689" rel="nofollow">https:&#x2F;&#x2F;x.com&#x2F;scottew&#x2F;status&#x2F;1751357591375208689

        The difference is that Costco pays their employees well enough to keep them around (notice that Costco prints the start year on each employee badge- average retail length of service is 1 year, Costco keeps people around for decades) and so they can learn to use this older software and master it. Most retail operations optimize their inventory management for new people, because they don&#x27;t expect someone to stick around long enough to master it.

        My wife worked at a small regional chain of pharmacies that had an ancient MS-DOS based EHR system. And she mastered that system to the point where people would call her when she was home with me and ask her how to do something, and she would walk them through &quot;okay, hit tab three times then shift-F12 then enter the frabble and then alt-F3 to go to the next screen and enter the drabble.&quot; It was difficult to learn it, but if you mastered it you could do everything you needed to do from just muscle memory while you were on the phone arguing with the doctor&#x27;s office that their prescription was not correct and needed to be changed.

        Then the small chain got bought by a national player and their brand new GUI system was brought in. It was a lot easier to learn- discoverability was a lot higher with menus and drop-downs and all of that. But if you stuck around to master it, you could never be as fast as you could with the older system. And that emphasis on quickly integrating new employees- but lower payoff for experience in employees- was clear in every choice that national chain made. They wanted their employees to be completely interchangeable, which meant that they didn&#x27;t care if you had six months of experience or four years of experience or three decades of experience.

        1. hylaride · · focus · HN ↗
          Same story at my bank. Tellers used to speed run through a TUI, hitting tab and other key combos to accomplish things. Now it&#x27;s a long wait with them mousing around.
          1. xp84 · · focus · HN ↗
            The best thing about all character-based applications I&#x27;ve ever used is the keyboard buffer. Even if you&#x27;re using a TUI on a system that has a slow backend, it almost always blocked the thread and didn&#x27;t consume from the buffer during waits, so if you knew the sequence of keys was &quot;Total, F1, 1, Enter, Enter, Tab, 2125551234, F10, 1, Enter&quot; you could just enter all those keystrokes as fast as you could and the system would eventually catch up with you, meanwhile you were bagging a purchase or counting out the cash, whatever.

            The GUI also has lag - especially in the era of web-technologies-bloat, more lag than ever - but whether touchscreen or mouse there can&#x27;t be a buffer, so each lag requires you to stare waiting for the next UI to be drawn.

            1. kccqzy · · focus · HN ↗
              Unfortunately web-inspired TUI toolkits start to lose that property. Hit a key too fast, before the next screen runs code to attach its event listener? Sorry your key is lost.
              1. orthoxerox · · focus · HN ↗
                Clickable web GUIs that don&#x27;t lose your interactions are even worse. The email client I have to use at work buffers your &quot;mark as read&quot; click when it&#x27;s loading new letters and applies it to the one that&#x27;s under your cursor when it finishes loading them.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.