Probably 'bug' is not the best word, but many programmers definitely consider excessive complexity as 'bad design' (unless complexity is inherently unavoidable due to the very nature of the problem).
User friendliness and security are not the parts that are bad. "Piling them on" is the part that's bad. UX and security need to be considered from day one.
Great bug. Disappointing that they all consider it a bug in `file` though, rather than an insane design where printing a document relies on parsing the output of `file`!! Madness.
Isn't it considered a bad practice already? But same as with regular bugs, complexity is not something one can just stop doing. It's something to actively manage and take care of.
http://verticalsysadmin.com/blog/sysadmin-war-story-the-netw...
https://news.ycombinator.com/item?id=15258238
tldr; printers have a hardware cache for fonts that's cleared when rebooted, havoc ensues