I can give you another point why NOT using alpm at the current state:<br>
- API Interfaces still change a lot (all 2-3 weeks)<br>
- The interface still is &quot;ugly&quot;<br>- A lot of functionality is missing for a proper GUI client to be written<br><br><br>You have done a great work on the C# implementation. I actually dislike the thought of having mono on the base, not for the reason that c# is anything good or bad, but for the reason that c# / mono isn&#39;t complete. I wouldn&#39;t even consider it as feature complete, they&#39;re always behind the current C# standards, often for a year.
<br><br>I lately tried to port an application to GTK# (a quite complex client), but it already failed on backend system functionality. The program is completely .NET 2.0, and SHOULD work out with mono. I found some articles / post on their groups that this is a bug of mono - i don&#39;t think a framework should come in a stable version with broken functionality, neither it should need more than half a year (as it&#39;s for now already) to get fixed.
<br><br>I can see C# making the deal into one of the main linux application development languages, but the time hasn&#39;t come yet. All of the applications you mentioned were either broken when i tried them (muine), had a bad or even worse performance (beagle)
<br><br>Currently, i also don&#39;t see any advantage of C# compared to python. In linux i see disadvantages, since there isn&#39;t too much software around, and not too many libs you can use. Also, we would set on a language which is not very popular in the linux community. As i know, C# has not even open standards.
<br><br>Yours,<br>STi<br>