I know that now, but there are still some .NET developers that I meet that think this is the way to go. Another problem with .NET is that there is a lot to lea

I know that now, but there are still some .NET developers that I meet that think this is the way to go. Another problem with .NET is that there is a lot to learn, then unlearn - language, api, frameworks, deployment-wise. That by itself is not bad, if you are an active developer, but if you just given few times a year to fix this and that C# project, then it's a bit more painful. For example I have to upgrade 32-bit app using Antlr3 and system.data.sqlite (matching 3.7.0.1) to 64-bit, antlr3 newer version and system.data.sqlite (matching 3.8.2) - and after the upgrade there is significant slowdown, and some things do not work (possibly sqlite, but who knows for sure).