3 ms·

I agree with you - and that's why I started out with "I understand what you're saying" - that it's not a common choice for Mac and Linux. But then again, I'd ar

I agree with you - and that's why I started out with "I understand what you're saying" - that it's not a common choice for Mac and Linux. But then again, I'd argue neither is Go, Rust or certainly Muon. .Net core is potentially going to fix this though. As for Go, Rust (and maybe Muon): I believe all of those have rough edges in cross-platform development too. Say - building nice UIs across platforms is still messy as far as I'm aware - and the C# cross-platform apps I mentioned (see: Banshee) struggled with that in the past as well. Definitely don't want to sound like a C# fanboy, although this is the stack I'm working with. I'm merely saying that is is a viable and improving option, so dismissing it in favor of a completely new language seemed odd. Not to knock Muon, but why can't they both co-exist and be equally viable?

tagrun 8y ago
Yes, FOSS in GNU/Linux distros are still written mostly C/C++. And I don't think C/C++ is going anywhere soon. What I'm saying is, Go and Rust are very new, but gaining traction fast for new projects, despite their low penetration as of 2019. I can't say the same thing for any implementation of C#. The concerns outlined here are still valid for the FOSS community today: https://www.fsf.org/news/dont-depend-on-mono https://www.fsf.org/news/dont-depend-on-mono https://www.fsf.org/news/2009-07-mscp-mono https://www.fsf.org/news/2009-07-mscp-mono And these are serious concerns given the context of Microsoft's hostile campaigns against FOSS, and EEE tactics against all competitors. What Oracle did with Java after acquiring Sun (Oracle vs Google) only justified and strengthened these concerns. The way I look at it, it's a risk that is not worth taking, especially given the alternatives today.