>unlike your implication that it is objectively crap for ignorant idiots.
I intended to communicate that it's crap in general.
>It's not like badly made food with lots of additives, preservatives, second rate ingredients, sodium and saturated fats is a constitutional right.
I believe that it is everyone's right to do what they want to their own bodies. Education lets people make the right decisions. Rules take away a person's right to make decisions. Maybe it's a constitutional right where you live or maybe not, but the law is not in line with common sense much of the time anyway.
>Also consider all the code needed to implement the "fluid GUI" you mention, with menus that can be shown as ribbons, regular toolbars or what have you by user choice. More code: more bugs, more costs, more complexity.
We're on the same page with more code being more costly but I'd argue that that's exactly what we're doing with the current customized UI's! By implementing this stuff at the library level instead of tens of thousands of implementations of custom UI's at the application level, we, in effect, reduce the amount of code. Since the population using the implementation increases, there is more testing and any bugs get squashed more quickly.
>There are, and they are very real --telephone support costs from people accidentally switching their UI to some other style is an obvious example.
That's the issue I have with this approach - everything comes down to business costs. In other words, the utility that something has to a small segment of society (the company) becomes more important than the utility it has to everyone else. This, to me, suggests an organizational structure which is broken by design.
>This again implies that only the programmer's job has thinking involved in it.
I'll concede this point and rephrase it - programmers are good at abstraction and saving work in the long run. This needs to be utilised more often than it currently is, particularly in terms of design.
I'm quitting smoking so I apologise for the tone of some of these posts.
I intended to communicate that it's crap in general.
>It's not like badly made food with lots of additives, preservatives, second rate ingredients, sodium and saturated fats is a constitutional right.
I believe that it is everyone's right to do what they want to their own bodies. Education lets people make the right decisions. Rules take away a person's right to make decisions. Maybe it's a constitutional right where you live or maybe not, but the law is not in line with common sense much of the time anyway.
>Also consider all the code needed to implement the "fluid GUI" you mention, with menus that can be shown as ribbons, regular toolbars or what have you by user choice. More code: more bugs, more costs, more complexity.
We're on the same page with more code being more costly but I'd argue that that's exactly what we're doing with the current customized UI's! By implementing this stuff at the library level instead of tens of thousands of implementations of custom UI's at the application level, we, in effect, reduce the amount of code. Since the population using the implementation increases, there is more testing and any bugs get squashed more quickly.
>There are, and they are very real --telephone support costs from people accidentally switching their UI to some other style is an obvious example.
That's the issue I have with this approach - everything comes down to business costs. In other words, the utility that something has to a small segment of society (the company) becomes more important than the utility it has to everyone else. This, to me, suggests an organizational structure which is broken by design.
>This again implies that only the programmer's job has thinking involved in it.
I'll concede this point and rephrase it - programmers are good at abstraction and saving work in the long run. This needs to be utilised more often than it currently is, particularly in terms of design.
I'm quitting smoking so I apologise for the tone of some of these posts.