Hacker Newsnew | past | comments | ask | show | jobs | submit | Timwi's commentslogin

The article spends a lot of time talking about how UIs “look” and how they all “look different”. That's not the important aspect to me.

For me what makes a software usable in the long run (after initial learn) is shortcuts and keyboard navigability. Old GUI frameworks had built-in features for this (app-wide shortcuts, underlined letters, etc.). The web has haphazardly copied one of them (“accesskey” attribute), but now this has been completely forgotten. None of the major websites have accesskeys, even for the most frequently used element like the search bar. There are no shortcuts for frequently used functions such as “like”, “reply”, what have you. It's like developers have universally forgotten that the keyboard exists and what it can do.

TUIs don't solve that.


Because by walking off the edge they will injure themselves.

What makes WhatsApp superior to Telegram and/or Signal?

It wasn't inherently yellow, it was the inverse of whatever it was on top of, but since the main window filling most of the screen was dark blue, it looked bright yellow most of the time.


My needs as a user are for a UI to be consistent and predictable.

Good luck.


To be fair, I didn’t say it was a _good_ idea…


No. For most of human evolution, we were hunter-gatherers. Imagine trying to hunt game with the accuracy of LLMs. You'll starve. Picking edible fruits from plants also requires precision, both in terms of the hand/eye coordination of actually picking it as well as in terms of knowing what's edible and what's poisonous.

When you fill up your coffee cup in the morning, I sure hope you aim accurately and don't pour half of it all over your desk. And don't even get me started on the process of making coffee that isn't completely unpalatable.


Do you have a source for that claim? I'm curious. I genuinely thought it was the OSA.


I believe you misunderstood them. The way I interpreted it is: 1) the development is already done, so the developers have broad consensus on how it should work; 2) the only thing that can break that consensus is a new RFC that tells them in no uncertain terms to do it differently.


Oftentimes the important data that needs restoring is in the checkout: uncommitted and unstaged changes that represent hours of work.


Word boundaries are one way to address that, but they require you to list all the inflections (and you missed “fixing”). Another way is to say (?<!de)bug.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: