{ "success": true, "comment": "\x3cdiv class=\"comment comment-published odd\"\x3e\n\n  \x3cdiv class=\"clear-block\"\x3e\n      \x3cspan class=\"submitted\"\x3eSun, 2009/03/08 - 1:54pm — \x3ca href=\"/users/4bugzilla\" title=\"View user profile.\"\x3e4bugzilla\x3c/a\x3e\x3c/span\x3e\n  \n  \n  \x3cdiv class=\"comment-score-div\"\x3e\n      \x3cspan class=\"comment-score-label\"\x3eScore: \x3c/span\x3e\x3cspan class=\"comment-score\"\x3e-5\x3c/span\x3e\n    \x3c/div\x3e\n\n  \x3cdiv class=\"comment-voting-controls\"\x3e\n    \x3cspan class=\"comment-promote\"\x3e\x3c/span\x3e \x3cspan class=\"comment-bury\"\x3e\x3c/span\x3e\n  \x3c/div\x3e\n\n  \n    \x3ch3\x3eAmarok developers ... remember, we\'re the experts!\x3c/h3\x3e\n\n    \x3cdiv class=\"content\"\x3e\n      From the post\r\n... and also some for usability reasons (such as the tabular playlist design - remember, we\'re the experts!).\r\n\r\nOh please don\'t try to convince that everybody are fools and just don\'t get it. There are 2 features that Amarok users mostly hate in 2.x series:\r\n1. Large central area with context information.  \r\n2. New play list.\r\n\r\nI remember history of both these new \"features\". Initial motivation of placing context info at the center was that Amarok developers believe that this context related stuff is really a central thing that distinguishes Amarok from other player. But all users ask is to place playlist next to the collection browser so that it was easier to drag items to playlist. \r\n\r\nThe mock up for new playlist was introduced long time before any real usability expert worked on Amarok 2. And current playlist is almost exact copy of that mockup. A lot of usability experts say that it is more natural for people to understand information if it is in the table. All usability experts say that that it is easier for human eyes to accept information by lines. There is no real usability reason to have current playlist. Not even saying about having some \"context\" space between collection and play list.\r\n\r\nIn free software world developers make all decisions because they really write code. That\'s fair. And that\'s the only reason for current Amarok 2.x UI. There are no real usability reasons for this.\r\n\r\nI am ok with statement that \"We write Amarok so we decide how it looks\". Why can\'t you just say this. But I really don\'t like when 10 people say to few hundreds of people that \"we are the experts and we know better\". To say this you need to be a real expert. If someone don\'t write any code for Amarok it doesn\'t means he is not an expert. Or he doesn\'t know what he is talking about. I am senior software developer. But I don\'t want to start writing code for Amarok only for purpose so my voice as well as voice of large number of other people was heard.\r\n\r\nHow many times amarok users must say something so that amarok developers at last started to listen???          \x3c/div\x3e\n  \x3c/div\x3e\n\n  \x3c/div\x3e\n" }