4 ms·
Because then you will have an interface that has been goaded into acting and drawing like you want it to, instead of having an interface which looks and acts in
by marssaxman 10y ago
Because then you will have an interface that has been goaded into acting and drawing like you want it to, instead of having an interface which looks and acts in ways which feel normal and familiar to users of the target platform.
Maybe you want that, as an app developer, but as a user I'd really like it if you'd stop, and I'm happy when the platform makes this sort of thing difficult.
- nurettin 10y agoWhat really changed my mind was the MLOC delphi application I maintain as part of my dayjob. People don't think "oh wow I wish this was a ctrl-v instead of shift-ins and what am I ever gonna do if this file dialog looks kinda weird and unfamiliar? and oh no, the context menu in this grid is actually a window with a handle and not the default menu that was originally intended by the win32 api gods? Give me cancer or give me death" No, they just busily work X hours and go home. They only care about getting their job done and if that means getting used to the interface they do so. We actually have users who've been around for about 20 years and you should see how fast they can enter some of the stuff.
- marssaxman 10y agoWell, sure, employers are free to waste their employees' time and make their lives complicated in all sorts of ways; that's what the paycheck is for. So what? It's still a crappy way to design apps, and I'm not going to respect it just because people successfully get away with it.