https://bugs.kde.org/show_bug.cgi?id=265567 --- Comment #40 from Modestas Vainius 2011-05-19 08:55:55 --- It surprises me how people think that Amarok 1 development model was not any different. You know people kept losing database too, Amarok 1 kept missing some files (or not finish scanning DB), it was slow and it could crash in various weird ways under normal usage. However, back then SQLite (upstream) was blamed for that even if a couple of DB indices were missing to speed things up. But Firefox, Android and other big software names were able to utilize SQlite perfectly and preserve people data for years and after numerous (major) upgrades. Now when Amarok 2 switched to MySQL, some other abstract "upstream" is being blamed for the same issues. So generally you might prise Bangarang (not that I know anything about it) but don't give Amarok 1 too much credit in this area. It would not be fair. P.S. I know that I'm sorta trolling in this bug report. But that's how Amarok development looked and still looks to me from the "outside" while still having to deal with complaints of frustrated users (not that I can help them :/). -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.