Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

No. It's just a matter of having advanced options or not. Each level of customization should be progressively more hidden but more powerful.


But where do you draw the line? What constitutes an "advanced option" worthy of dedicated UI rather than a customised build? What proportion or minimum number of users have to find it valuable for the effort and lost simplicity to be justified? When there are too many advanced options to manage sensibly, do we move to "advanced", "really advanced" and "actually quite scary you even thought of this" options?


Love to know how numbers of users affected is measured. One of the arguments is that with a large enough number of users (millions) an option can cause significant numbers of people grief if they misuse it.

Same argument can be said for removing a feature 2% of the population of users rely on. 2% of 450 million users is 9 million users. Not what I'd call a tiny number of users.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: