3 ms·
I share the same sentiment to the many others here in opposition. This is yet another datapoint on the insidious trend of dumbing down UIs and destroying user-i
by userbinator 6y ago
I share the same sentiment to the many others here in opposition. This is yet another datapoint on the insidious trend of dumbing down UIs and destroying user-individualism.
As a reminder of how much we've fallen, look at the appearance settings for Windows 95:
http://toastytech.com/guis/win95schemes.png http://toastytech.com/guis/win95schemes.png
You can change the colours, fonts, and sizes of all the UI elements, and have everything looking exactly the way you want, down to the pixel size and RGB value! That was possible 25 years ago, with the technology and computing power of the time, as well as developer effort.
For fun, I decided to open the linked site in IE6 with its default theme, and compare how its UI looks. In almost exactly the same vertical space taken by "Firefox Compact Current" which shows two lines of tabs (with cut-off titles), an address bar (with cut-off URLs), and navigation buttons, IE6 manages to fit four lines: [1] A full titlebar, [2] A menubar, [3] Navigation buttons, and [4] A full URL.
With current Firefox, you only get three choices: "large", "huge", and "WTF"; and Mozilla plans to remove the already-too-large choice to make it two. No doubt sometime in the future it will become one, if this trend continues.
What's more, the UI of IE will change size, font, and colour if I change them in the system's settings, so I can have the same consistent appearance throughout. If I want a huge UI, more interesting fonts, dark mode, or whatever else, I don't have to set it per-application, unless it's an application like Firefox which draws its own UI...
What happened? When an entity like Mozilla would rather spend a lot of effort on complicated site-facing features, yet remove already-trivial yet extremely useful configurations like these, it's really hard to not see that software is going backwards and becoming more user-hostile.
- ImprovedSilence 6y agoSo much truth. In fact, the reason I left firefox for chrome in (2008ish?) was precisely because chrome was more compact, and left more room for just the webpage. Now Firefox is at least competitive in that regard, and I use compact as well. But more to your point about customizability, for some god forsaken reason, I cannot set a keyboard shortcut so that command-: and command-; become previous and next tab. I uses this for every other tabbed program ever both mac and linux. But somehow in firefox i need something dumb like ctrl-shift-left or something. Thats the single biggest factor keeping me out of firefix. Getting rid of compact isnt going to help them either I suppose. Who is making these decisions for Mozilla, Google?
- meddlepal 6y agoThe trend towards killing desktop individualism started with Steve Jobs and Mac OS X Aqua interface. Making computing “pretty” became the imperative design criteria. That meant heavily curtailing what things people could customize.
- bob1029 6y ago>What happened? Building extremely high quality user interfaces has been de-prioritized by our tech gods. See: ElectronJS. Every "native" "desktop" application built upon such technologies has a minimum latency bound that is user-detectable and a memory appetite that cannot be appeased by even the most opulent workstation-class system. Those of us seeking client->server->client trips that are measured in microseconds (on top of network stack latency) have been forced into the dark nether-reaches of technology. Writing 2D graphics libraries and client/server UI frameworks from scratch has become one of my new favorite hobbies. All of this is especially upsetting when you consider how much complexity has been magically hand-waved away over the last 20 years with modern OS, language and tool design. You don't even have to go to C/C++ to get the UI performance these days. A high-quality C# implementation using platform-specific graphics interop is more than capable of producing UIs that can respond in the 10-1000 microsecond range. WinApi interop and hooking the window message pump is a trivial exercise. See: https://github.com/prasannavl/WinApi https://github.com/prasannavl/WinApi et. al.