Slashdot Mirror
How Apple Is Giving Design a Bad Name (theverge.com)
ColdWetDog writes: Co.Design has an article by two early Apple designers on how the company has lost its way, and quite frankly, lost its marbles when it comes to user interface design. In the search for a minimalist, clean design, it has forgotten time honored UI principles and made it harder for people to use Apple products. As someone who has followed computer UI evolution since the command line and who has used various Apple products for a number of years, the designers' concerns really hit home for me.
Of course, Apple isn't the only company out there who makes UI mistakes. And it is notable that the article has totally annoying, unstoppable GIFs that do nothing to improve understanding. User Interfaces are hard, but it would be nice to have everybody take a few steps back from the precipice.
Of course, Apple isn't the only company out there who makes UI mistakes. And it is notable that the article has totally annoying, unstoppable GIFs that do nothing to improve understanding. User Interfaces are hard, but it would be nice to have everybody take a few steps back from the precipice.
A lot of the functionality of the iTunes UI has fallen to the wayside.
I dread every iTunes update as I know I will have to change things back around to the way I like them from the way that Apple thinks I should like them.
And in a sort of related issue, the recent revelation that Siri won't answer music related questions unless you have a current subscription to Apple's music service is both worrisome and telling about the direction that Apple is taking.
I am Slashdot. Are you Slashdot as well?
Look again, please. systemd breaks stable network configurations by unnecessarily replacing dhcp, it breaks daemon-startup debugging, it breaks decades of log analysis tools designed to work with text based rather than proprietezed binary logging format, it's repeatedly broken kernel startups, it's broken the stable model of attached storage being mounted under /media, and the attempts to replace all of "/etc" with a "stateless Linux" model is breaking tools that never volunteered to have anything to do with systemd. It's also breaking cross-platform compatibility of daemon initialization configurations.
A "light Linux user" may not see these issues becuase you wouldn't necessarily be debugging failed daemons, writing cross-platform tools, or trying to integrate stable business software with this latest fad for configurations.