Hacker News Reader

If you are that particular about your tools you should consider making them yourself, or using software you can really claim ownership of. iTunes and Chrome are not your software in any meaningful sense. Even less so probably because they are free (gratis).

With Mozilla you might have a claim, and I assume you are free to make your own version that has the columns in your preferred order or whatnot. For official support you just have to convince a sufficient number of like-minded programmers that yours is a problem worth solving, and then some minor technical bits like "What determines the central theme?" and "What scripting language shall we standardize on?"

If my hardware (hard disk) has a particular configuration of bits stored on it then they are my bits. How can information stored on something I own not be mine? I'm not talking in the legal sense here, I think that patents are ridiculous, but in the common sense sense.

I can't tell if your original comment was more than a rant. In some sense you own those bits, but not in a way that is useful to you. Starting with just the bits, it's going to be a lot of work to make iTunes skinnable, and you likely won't be able to distribute your changes legally.

It seems similar to ranting that Miles Davis has recorded all of these long boring solos on _your_ CDs. You could spend your time editing them out, you could demand an edited reissue from the publisher, you could just listen to something else, or you could learn to play trumpet and record something you'd rather listen to. The least useful option seems to be posting to HN.

> I know what I want my user interface to look like. I know what fonts, colours and relative sizes I want things to be.

You do? Wow. I sure don't.

Designing an user interface is mostly not about picking your favorite font and color. It sounds like you use the word "design" for what is actually "theming" or "skinning".

  I know what fonts, colours and relative sizes I want things to be.

This is only tangentially related, but a few years ago I set up my web browser to default to white on black. Big mistake. I promptly found out that about half the websites out there specify a text color, but not a background color.

Customization needs to be actively supported. It rarely comes for free.

^ the truth. hurts, doesn't it.

>My computer is my computer. Not Apple's computer when I'm using iTunes (hah, as if I'd ever use that piece of crap, but stay with me here)

Yes, very funny. Well, I'm a CS graduate, and I have no qualm with using iTunes. My colleague in the next workstation is a PhD from Cambridge and he uses iTunes too. Might want to expand your horizons about what is a "generally accepted piece of crap" and what is a personal preference.

>I know what I want my user interface to look like. I know what fonts, colours and relative sizes I want things to be. All in exactly the same way that I know what colour I want the walls to be painted in my home and where I want my furniture. By breaking UI conventions because some idiot thinks that he knows what colours and shapes my monitor should display, I am unable to dictate what my own things should look like.

That you "know what you want" doesn't mean what what you want is also right for you. For example, every obese person that craves for McDonalds also, er, "knows what he wants". But it would be better for him, in the long term, if he was denied that.

Furthermore it's not just about "you" or "me".

For one, the "idiot" you refer to is the programmer, and he also wants to express himself in his product. If you don't like it, don't buy it.

Second, for UIs in general to evolve people must come up and try different approaches, and, yes, break for the conventions.

Third, your argument doesn't even make much sense. You say you "know what you want", but at the same time you despise programmers making customized UIs instead of following the OS guidelines.

It would surely make much more sense to despise OS companies making their UI guidelines.

For, if a programmer makes a custom looking app, you can buy something else, but if your OS vendor comes up with designs you don't like you have no recourse except some basic customizations (which might not even apply, e.g you cannot change how the menubar works or where it is placed on OS X) or the painful switch to a different platform altogether. So you have to suffer their UI decisions in almost every apps.

>To hammer the point in further with another example, CSS was designed with, err, designers in mind and look at what a head-fuck that turned out to be. Leave the thinking to people who know how to think - we'll tell you what needs prettying up and how to do it right.

The implication that designers don't know how to think is as idiotic as is preposterous.

And the insinuation that non-designer "thinker" can just "tell 'em what needs prettying up" and we'll get good GUIs (as if design work is mere "prettying up"...) is even more laughable.

>Yes, very funny. Well, I'm a CS graduate, and I have no qualm with using iTunes. My colleague in the next workstation is a PhD from Cambridge and he uses iTunes too. Might want to expand your horizons about what is a "generally accepted piece of crap" and what is a personal preference.

http://www.straferight.com/photopost/data/500/medium/double-...

Whoopdeedoo, you've got a degree! Congratulations! I got a C in German when I was 16 but I don't brag about it.

>That you "know what you want" doesn't mean what what you want is also right for you. For example, every obese person that craves for McDonalds also, er, "knows what he wants". But it would be better for him, in the long term, if he was denied that.

Where's that triple facepalm jpeg...

What would help an obese person, and anyone else trying to break a habit in the long term is education, not taking away their free will. If an obese person understands what causes his sugar cravings, why eating sugary food makes him fat and that eating sugar will spike his blood sugar levels and then cause them to crash which will then cause yet another craving, he will stop eating it and lose weight. If that same person is educated about amino acids and how L-Glutamine, a non-essential amino acid, can stop cravings dead in their tracks when taken as a supplement, he will take a spoonful of that instead of reaching for the junk food when a craving hits him. If, through experience, he learns that exercise makes you feel awesome and has that little side effect of bringing weight down, he'll be sold for life. Denying people their right to make choices is a weak attempt to control what is not ours. Education is the way forward.

To address the other points you made, programmers do not like customized UI's. That's something which designers come up with because they are a) not aware of standards and the implications of breaking them and b) take orders from management who are advised by marketing on how to make the product memorable. To quote those crazy Asian rappers, the Wu-Tang Clan - "Cash rules everything around me, C.R.E.A.M. - get the money, dollar dollar bills y'all!"

> but if your OS vendor comes up with designs you don't like you have no recourse except some basic customizations (which might not even apply, e.g you cannot change how the menubar works or where it is placed on OS X)

I agree that this is exactly what's wrong with the current GUI toolkits - those kinds of customizations should be implemented at the library level, not the application level. I.E. have a widget for a menu which a theme can render however the hell it wants. Hell, make themes applicable on a per-application basis since you might want a different style for, say, music production software or an IDE.

Besides, OS X is possibly the worst example of a customizable UI, save Gnome/GTK. Almost none of it is customizable by design. I swear, Apple products are completely brain damaged.

> The implication that designers don't know how to think is as idiotic as is preposterous.

Just as the implication that programmers can't design is idiotic and preposterous, not that anyone would ever claim such a thing. Nonetheless, they completely suck at it - http://www.davelgil.com/BC_placeholder.png Just as designers can think but completely suck at that. If they would just combine forces and form into a bigger and better machine...

> And the insinuation that non-designer "thinker" can just "tell 'em what needs prettying up" and we'll get good GUIs (as if design work is mere "prettying up"...) is even more laughable.

But that's exactly what happens even with web UI's - the programmers define the structural elements - e.g. this is a button, this is a list - and the designers skin those widgets. You can't paint a structure which doesn't exist!

Auf Wiedersehen.

>Whoopdeedoo, you've got a degree! Congratulations! I got a C in German when I was 16 but I don't brag about it.

No, you only brag about how idiotic a) programmers that design custom UIs and b) designers in general are compared to you. Anyway, my point, which apparently went whoosh wasn't to brag (lotsa people have CS degrees), it was to show that even people trained in CS can find iTunes OK --unlike your implication that it is objectively crap for ignorant idiots.

>What would help an obese person, and anyone else trying to break a habit in the long term is education, not taking away their free will. If an obese person understands what causes his sugar cravings, why eating sugary food makes him fat and that eating sugar will spike his blood sugar levels and then cause them to crash which will then cause yet another craving, he will stop eating it and lose weight.

I don't see this "educate them" thing working wonders in the US. Plus it's not about taking away his "free will", just his junk food. He can still "will for it" it as much as he likes. It's not like badly made food with lots of additives, preservatives, second rate ingredients, sodium and saturated fats is a constitutional right.

>To address the other points you made, programmers do not like customized UI's. That's something which designers come up with because they are a) not aware of standards and the implications of breaking them and b) take orders from management who are advised by marketing on how to make the product memorable.

You'd be surprised. I'm a programmer. So is Will Shipley. So are tons of other, er, programmers that happen to like customized GUIs. Being a programmer is orthogonal to liking customized GUIs.

>Besides, OS X is possibly the worst example of a customizable UI, save Gnome/GTK. Almost none of it is customizable by design. I swear, Apple products are completely brain damaged.

A UI being "brain damaged" is also orthogonal to it being non customizable. You write as if there were no engineering and UI tradeoffs in a customizable UI. There are, and they are very real --telephone support costs from people accidentally switching their UI to some other style is an obvious example.

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.

>Just as the implication that programmers can't design is idiotic and preposterous, not that anyone would ever claim such a thing. Nonetheless, they completely suck at it. Just as designers can think but completely suck at that.

This again implies that only the programmer's job has thinking involved in it. Which is as far from the truth as it can be. But check me response below for more:

>But that's exactly what happens even with web UI's - the programmers define the structural elements - e.g. this is a button, this is a list - and the designers skin those widgets. You can't paint a structure which doesn't exist!

In 1996 maybe. It's 2012. It hasn't been done like that for ages. If anything, with modern UX emphasis, it has got to the opposite: the designers design all the structure, interactions and functionality and the backend programmers have to implement it. But in the best web shops it's 50-50.

>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.