Live data from Hacker News

Learning from Terminals to Design the Future of User Interfaces

brandur.org

61–70 of 379 posts

Re: Learning from Terminals to Design the Future of User Interfaces

#61
One of the failures of modern GUI design is exemplified by the calculator app on the iphone. It looks exactly like the old stand-alone desktop calculators. What could be wrong with that?

Have you ever used a calculator, and wondered if you'd punched in the operands correctly? I have. And so I do the calculation again.

With a scrolling terminal, you can see (and check) the operands on the previous line(s).

Re: Learning from Terminals to Design the Future of User Interfaces

#62
post #60

Earlier quoted context omitted.

I think your criticism misses the mark. [1] You're answering an article that starts with a 45-second video of Slack opening (surely the worst offender among modern apps) with something about latencies measured in thousandths of a second. [2] As Nielsen is focused on web apps and applications, this advice is less applicable to UI provided by the OS that you interact with all day in presumably familiar ways. Note that…

> 45-second video of Slack opening (surely the worst offender among modern apps I hate to defend Slack as it's far from snappy, but comparing it to a console app seems hardly fair. I wonder how much of it's slowness is due to network requests? I could make the argument that git is slow because when I clone a large repository it takes a while.

I do not see how that comparison is unfair. Terminal IRC clients, for example, accomplish the same exact functionality as Slack in a curses UI in a vastly faster way.

Re: Learning from Terminals to Design the Future of User Interfaces

#63
post #6

Yes! I am so glad somebody called out the UI animations! The one in 1Password bugs me every time, I don't use Spaces because it takes too long for the animations to play out. There are more examples. Every time a programmer adds an animation, a settings option should also be added to "disable animations". Advanced users will love you for it!

Animations are cool the first time you see them. The tenth time, they are just aggravating.

Re: Learning from Terminals to Design the Future of User Interfaces

#64
I highly disagree that the animations are superfluous for the vast majority of users. Yes, they can be superfluous, but that's not by their nature of existing.

History shows us that consumers value good UX, of which animation is a key component. The iPhone wasn't the first smartphone, but it was the fist one to take UX as seriously as the hardware.

As for the examples:

- Slack: Yes, it takes forever to load and I hate that, the real problem is performance, not the animation. Would it be better if no animation happened and didn't inform the user about about what's going on? Keep in mind that the animation also serves to inform the user that it hasn't "frozen", so a still interstitial would be a regression.

- Spaces: The animation tells the user what is going on! Having the entire screen change instantly would be confusing for the vast majority of users.

I do value choice though, so perhaps there should be a setting for power users to disable/minimize them.

Re: Learning from Terminals to Design the Future of User Interfaces

#65
post #60

Earlier quoted context omitted.

> 45-second video of Slack opening (surely the worst offender among modern apps I hate to defend Slack as it's far from snappy, but comparing it to a console app seems hardly fair. I wonder how much of it's slowness is due to network requests? I could make the argument that git is slow because when I clone a large repository it takes a while.

I do not see how that comparison is unfair. Terminal IRC clients, for example, accomplish the same exact functionality as Slack in a curses UI in a vastly faster way.

But somehow there's all these people that want to use Slack over Irssi.

Re: Learning from Terminals to Design the Future of User Interfaces

#66
post #60

Earlier quoted context omitted.

I think your criticism misses the mark. [1] You're answering an article that starts with a 45-second video of Slack opening (surely the worst offender among modern apps) with something about latencies measured in thousandths of a second. [2] As Nielsen is focused on web apps and applications, this advice is less applicable to UI provided by the OS that you interact with all day in presumably familiar ways. Note that…

> 45-second video of Slack opening (surely the worst offender among modern apps I hate to defend Slack as it's far from snappy, but comparing it to a console app seems hardly fair. I wonder how much of it's slowness is due to network requests? I could make the argument that git is slow because when I clone a large repository it takes a while.

This goes to the article's point about caching; a chat app -- of all programs -- should cache conversations for a fast boot up. Sure, _updating_ the conversations -- the "cloning" stage -- may take some time, but why should you have to wait for the network requests to complete before seeing your past conversations?

The git equivalent would be if you had to wait for git to do a fetch/pull every time you ran "ls" on a git-controlled folder. It would be insane, and no one would use git (or any other version control).

Re: Learning from Terminals to Design the Future of User Interfaces

#67

I'm switching away from macOS to Linux with the i3 window manager for precisely this reason. But all of his criticisms of terminals are spot on: no multimedia, no support for anything other than monospaced fonts, etc. Lord, somebody give me a terminal program that produces laid-out text and can show inline video.

The old Symbolics Genera had a "terminal" which was extremely interactive and object based, yet still worked much like a modern text only terminal. I still love working in that operating system. Pictures, fonts, diagrams, etc., were all supported well. I have not tried video nor seen examples of it but those computers were responsible for some CGI in movies in their time, so may have been supported.

Re: Learning from Terminals to Design the Future of User Interfaces

#68
I had sort of an "aha" moment reading a non-technical co-workers conversation on Slack the other day. Someone built a Slackbot to show the menu for whatever food truck is outside our building that day, and people could use it just by typing "/foodtruck". They were blown away and loved it. Rather than opening a browser and navigating some disparate menu pages, they could simply fire off a command in their "console".

I realized that people love Slack because it has introduced them to the CLI paradigm of computing for the first time. CLI is so much more efficient and powerful if users can somehow be incentivized to put in the time and effort to become productive, which Slack has focused on a lot. As inefficient and silly as it may seem to us developers, Slack with it's endless command based integrations has succeed wildly at that where nothing else has so far.

Re: Learning from Terminals to Design the Future of User Interfaces

#69
post #65

Earlier quoted context omitted.

I do not see how that comparison is unfair. Terminal IRC clients, for example, accomplish the same exact functionality as Slack in a curses UI in a vastly faster way.

But somehow there's all these people that want to use Slack over Irssi.

Probably because IRC is an outdated protocol with inferior features to Slack and very few good open source options for connecting. For example:

* DCC is still unreliable.

* There is no audio connection option, which is quite popular in 2018.

* Channel history management is ad hoc

* Authentication is done in band, in plain text.

* "secured" channels rely on this bad authentication, and if they don't (perhaps electing to manage it themselves) network flaws can completely steal your channel.

* IRC isn't even particularly open source, many servers and networks have private patches that are not shared publicly.

IRC isn't better than slack. I agree with you that it's confusing why people suggest that it ought to be.

Also, most IRC networks are controlled by entities even more inscrutable than Slack's executive team and board. I can go look up who runs slack, I cannot actually find good details on who runs any given IRC network. I have no idea what I'm dealing with or how they're using my data. I have no legal recourse if I do discover bad behavior, and I'm forced by the ossified protocol to keep using their insecure authentication mechanisms which make abuse trivial.

Re: Learning from Terminals to Design the Future of User Interfaces

#70
post #6

Yes! I am so glad somebody called out the UI animations! The one in 1Password bugs me every time, I don't use Spaces because it takes too long for the animations to play out. There are more examples. Every time a programmer adds an animation, a settings option should also be added to "disable animations". Advanced users will love you for it!

> Every time a programmer adds an animation, a settings option should also be added to "disable animations".

You can disable every animation in OS X itself via the command line (defaults write). I put them all in a shell script that I run on new installs. You may be out of luck with 1Password.

Post reply on HN