4 ms·

You are correct, it uses Mono. I am a little behind the times these days (used debian/ubuntu for a few years of laptop use), but this article seems to have a n

You are correct, it uses Mono. I am a little behind the times these days (used debian/ubuntu for a few years of laptop use), but this article seems to have a number of links to the issues, which date back to April 2009. http://techrights.org/2009/10/22/disinformation-about-banshee/ http://techrights.org/2009/10/22/disinformation-about-banshe... Too bad Amarok is KDE and not Gnome, it is such a better music player and doesn't carry the MS/Novell stigma (just QT/KDE).

cookiecaper 16y ago
Have you used Amarok 2.x? It's different than Amarok 1.x. Lots of people don't like it. There are a few projects out there whose purpose is to clone Amarok 1.x and continue development (Clementine is one). Not sure why people didn't just fork it, but whatever. The Mono thing is tricky because MS could at the very least drag it through a hellish tangle in the court system with all the MS-held .NET oriented patents out there. MS doesn't have Sun to keep them in check anymore and as Windows declines they'll get increasingly desperate and start targeting open systems. They snuggle up to de Icaza and Novell now when they don't think they're a threat, but if that situation changes MS and Mono will be mortal enemies, technically and legally. MS's whole life is about promoting Windows. At the moment Mono is seen as a way to get more people into C# dev, because MS believe they have the best tools for C#/.NET dev (Visual Studio) and you need Windows to run them. If you get a bunch of OSS hackers on C# and .NET, when they need some extra cash they'll take a freelance job and use/buy Visual Studio and/or C#. Things won't always be that way, though. Mono is kind of a wildcard because everyone knows subconsciously that when MS gets desperate enough they'll be out to squeeze as much blood as possible from patent infringement suits, etc. related to Mono. They may seize the opportunity to try to kill Canonical or other relevant players in the not-Windows market. That said, I think it's fine to use it for now. :)

cookiecaper 16y ago

Have you used Amarok 2.x? It's different than Amarok 1.x. Lots of people don't like it. There are a few projects out there whose purpose is to clone Amarok 1.x and continue development (Clementine is one). Not sure why people didn't just fork it, but whatever. The Mono thing is tricky because MS could at the very least drag it through a hellish tangle in the court system with all the MS-held .NET oriented patents out there. MS doesn't have Sun to keep them in check anymore and as Windows declines they'll get increasingly desperate and start targeting open systems. They snuggle up to de Icaza and Novell now when they don't think they're a threat, but if that situation changes MS and Mono will be mortal enemies, technically and legally. MS's whole life is about promoting Windows. At the moment Mono is seen as a way to get more people into C# dev, because MS believe they have the best tools for C#/.NET dev (Visual Studio) and you need Windows to run them. If you get a bunch of OSS hackers on C# and .NET, when they need some extra cash they'll take a freelance job and use/buy Visual Studio and/or C#. Things won't always be that way, though. Mono is kind of a wildcard because everyone knows subconsciously that when MS gets desperate enough they'll be out to squeeze as much blood as possible from patent infringement suits, etc. related to Mono. They may seize the opportunity to try to kill Canonical or other relevant players in the not-Windows market. That said, I think it's fine to use it for now. :)