651–660 of 944 posts
Earlier quoted context omitted.
> There's no benefit gained, whatsoever, from moving content to the title bar. There is: more space for content, e.g. websites while not removing directly accessible functionaly
If things are so tight in the layout that taking the title bar away is actually necessary, then the layout is already fundamentally bad.
Earlier quoted context omitted.
I am coming to the opinion that Windows XP was the maximum usable interface, and we should have stopped there [0]. But then, I might just be old and telling the kids to get off my lawn. [0] this is definitely true for Windows. All subsequent versions of Windows have had worse UX.
I thought Windows 7 was pretty good. Vista eliminated the Fisher Priceness of XP but added a whole bunch of glowing and reflective stuff, which Windows 7 toned down dramatically. I don’t remember if Win 7 still allowed you to have the classic start menu, but I do believe I was ok with what it did have.
Earlier quoted context omitted.
And on the flip side, Chrome - just had the biggest laugh when I got to this point: "Imagine being able to configure anything useful in chrome ever." Overall, a very well written article - kudos to the author. (I've made the switch to FF again myself after Edge just got too annoying with their constant nagging about Bing search and other features. And the prompt to restore tabs. Just STFU and stop it already.)
One useful thing you can enable in Chrome is tab bar scrolling. Without this setting the tab bar is broken by default, if you open too many tabs on it the bar will simply not show some of them because there's no room left, while all remaining ones are just a few pixels wide.
It’s very funny and strange that one of the defining characteristics of modern GUI design is that everything is very large. Lots of whitespace, buttons twice as tall as the cursor, windows that have to be maximized in order to see more than seven lines of content, and yet the scrollbars are the size of a toothpick.
I suspect both of those trends are related to designing mobile-first.
Earlier quoted context omitted.
I often wish we had more analog control in the digital world. I wish there were turn knobs instead up/down buttons with 10 steps (where it is easy to accidentally leave a menu... When trying to get back to where you were, you are suddenly adjusting something else entirely). Manual control with digital devices has become too digital and too cumbersome. It used to be easy to adjust contrast and brightness on a display,…
And when you finally have a along controls everything is overloaded. Dish forced a new remote on us last time a device broke and they replaced it. It has far fewer buttons. I’m sure it helps getting familiar with it on a super basic level. But the old one wasn’t that complicated anyhow. But here’s the kicker: there’s no fast forward or rewind buttons. There no stop button. No record button. All of these (and more) ha…
Earlier quoted context omitted.
I like telegram's slick UI library. making an app using it would be nice. That and stickers, reaction emojis (which I also like in Slack, and teams only lets you have one reaction) calls, video, screen sharing, animated stickers, premium-stuff however... all junk.
Telegram is Qt based as far as I know. Funny that I would find the other basic comms channels integrated a good thing, if they would be properly polished, and the stuff you like is what I find junk.
Earlier quoted context omitted.
Ironic, to some degree. I agree with the overall sentiment,but: > There's no benefit gained, whatsoever, from moving content to the title bar. But also: > Chesterton's Fence >>The more modern type of reformer goes gaily up to it and says, 'I don't see the use of this; let us clear it away.' To which the more intelligent type of reformer will do well to answer: 'If you don't see the use of it, I certainly won't let yo…
> By moving things to the title bar, you gain back some real estate that you can dedicate to this ever expanding set of other tools and content. But the loss of the title bar causes actual pain and interferes with practical use. It's hard to imagine any tools/content that would be worth that loss.
Earlier quoted context omitted.
Screens can get brighter now, but if your screen is too bright, that's entirely on you. Adjusting the brightness is trivial and you can even do it without using the buttons on the display (DDC/CI).
This is something that has always boggled my mind. >Gee, this stark white brightness is hurting my eyes, maybe I should turn down the brightness on my display... >Nah, I'll just demand every single company completely overhaul the CSS and contrast of everything while begrudgingly suffering the eye-burning whiteness of companies that haven't yet overhauled their CSS Like wtf?
Earlier quoted context omitted.
Telegram is Qt based as far as I know. Funny that I would find the other basic comms channels integrated a good thing, if they would be properly polished, and the stuff you like is what I find junk.
How do you know? It seems Telegram Web looks very similar
But having checked clients for other platforms they are not made with Qt. You can check them all here: https://telegram.org/apps
Earlier quoted context omitted.
And when you finally have a along controls everything is overloaded. Dish forced a new remote on us last time a device broke and they replaced it. It has far fewer buttons. I’m sure it helps getting familiar with it on a super basic level. But the old one wasn’t that complicated anyhow. But here’s the kicker: there’s no fast forward or rewind buttons. There no stop button. No record button. All of these (and more) ha…
The worst offender of this is the Apple TV remote. Most of my actions with the Apple TV remote have been unintentional.
It's really a shame how user-hostile design can be.