3 ms·
Back in the 90s, you had a setting for everything! It was glorious. This trend of deliberately not making things configurable is the worst, and we can’t seem to
by ryandrake 11mo ago
Back in the 90s, you had a setting for everything! It was glorious. This trend of deliberately not making things configurable is the worst, and we can’t seem to escape it because artists are in charge of the UI rather than human interaction professionals.
App designers need to understand that their opinions on how the app should look and work are just that: opinions. Opinions they should keep to themselves.
- 3v1n0 11mo agoTry to maintain the whole matrix or possibilities then you tell me...
- eviks 11mo agoIndeed, people aren't paid to do the good things, only the easy ones
- rcxdude 11mo agoWhich is why you should think about how these options interact and compose at the start, as opposed to only adding options in an ad-hoc manner (whether you do it willy-nilly or only when your arm is really twisted)
- hulitu 11mo ago"You mean we shouldn't use 10 layers of abstraction and 274 libraries to achieve our goal ? I mean, we use a lot of resuources, but look how polished the UI is: everything is flat. " Thank god the RAM prices have risen. Maybe some people will start to programm with their heads instead of their (AI) IDE.
- array_key_first 11mo agoIt does make quality assurance an absolute nightmare, I would know, our application is like this to the 10th degree. Config on top of config on top of setting on top of options. But if you also want your product to be productive for a way array of use cases, it's necessary. You need to think about your market.