Is Xamarin moving away from the base mono-project? I mean it as an honest question, not a troll. The 3.2 release seems mostly aimed at mobile development and cutting off support for previous major versions (2.10 and 3.0). Further, there was never an official stable release of 3.0. It's their choice if they want to and they've done great service for the community with what they've already done. But if they've changed…
Mono 3.0 stable has been out for a while. There just wasn't many binaries for it so you have to compile it yourself mostly.
Mono 3.2
61–70 of 70 posts
Re: Mono 3.2
#62Is Xamarin moving away from the base mono-project? I mean it as an honest question, not a troll. The 3.2 release seems mostly aimed at mobile development and cutting off support for previous major versions (2.10 and 3.0). Further, there was never an official stable release of 3.0. It's their choice if they want to and they've done great service for the community with what they've already done. But if they've changed…
Re: Mono 3.2
#63Earlier quoted context omitted.
Mono 3.0 stable has been out for a while. There just wasn't many binaries for it so you have to compile it yourself mostly.
Their download page indicates that 2.10 is the last stable version. http://www.go-mono.com/mono-downloads/download.html
In another HN discussion, a person from Xamarin said they didn't have the resources to keep Linux package management up-to-date.
However, they scored $16 million in funding this month, so going forward they certainly do have the resources.
Re: Mono 3.2
#64I like C# and I'm impressed with Mono but there is just something not right. It might be irrational but knowing that Microsoft's DNA is everywhere makes me feel uncomfortable. I'm also not happy that Linux is a second class citizen - there is no Xamarin Studio for Linux, the latest version of MonoDevelop is not packaged for Linux, and the latest version of Mono 3.2 is only packaged for Mac as an easy download. The id…
GTK# is what is used to develop Xamarin Studio / MonoDevelop, so it is pretty well supported.
Re: Mono 3.2
#65Earlier quoted context omitted.
> Mono never succeeded on Linux because it always felt like a second-class citizen on the desktop Err, I'm not sure where you were from 2005 to 2009... There were apps like Tomboy that were included in GNOME releases that were 100% written in C# and run by Mono. GTK# was one of the most complete bindings ever written for GNOME/GTK. If you've ever written a GObject or GTK based app you would know its not easy to do in…
For gtk at the moment the "main" language is becoming Vala, who is more... mh, trusted than mono and strongly more supported by all the gtk developers
Re: Mono 3.2
#66Earlier quoted context omitted.
> Mono never succeeded on Linux because it always felt like a second-class citizen on the desktop Err, I'm not sure where you were from 2005 to 2009... There were apps like Tomboy that were included in GNOME releases that were 100% written in C# and run by Mono. GTK# was one of the most complete bindings ever written for GNOME/GTK. If you've ever written a GObject or GTK based app you would know its not easy to do in…
For gtk at the moment the "main" language is becoming Vala, who is more... mh, trusted than mono and strongly more supported by all the gtk developers
Re: Mono 3.2
#67I like C# and I'm impressed with Mono but there is just something not right. It might be irrational but knowing that Microsoft's DNA is everywhere makes me feel uncomfortable. I'm also not happy that Linux is a second class citizen - there is no Xamarin Studio for Linux, the latest version of MonoDevelop is not packaged for Linux, and the latest version of Mono 3.2 is only packaged for Mac as an easy download. The id…
> I like C# and I'm impressed with Mono but there is just something not right. It might be irrational but knowing that Microsoft's DNA is everywhere makes me feel uncomfortable. (...) I'm also not happy that Linux is a second class citizen The first kind of thinking is what got us into the second kind of situation. Enjoy ...Vala.
Re: Mono 3.2
#68> "Google contributed ports of NaCl for ARM and Amd64." So, Mono/C# in Chrome? If NaCl/PNaCl becomes available outside the Chrome App Store, that could be pretty exciting -- Mono does an excellent job with AOT performance and mobile-scale memory utilization.
Re: Mono 3.2
#69> "Google contributed ports of NaCl for ARM and Amd64." So, Mono/C# in Chrome? If NaCl/PNaCl becomes available outside the Chrome App Store, that could be pretty exciting -- Mono does an excellent job with AOT performance and mobile-scale memory utilization.
It would be great to hear more about this, are there any 'Hello World' examples? I assume the API's that NaCl-exposed have a corresponding set of C# interfaces? How does one write to the browser window, get user input, network I/O, etc?
That post is old, but the instructions are still valid.
> I assume the API's that NaCl-exposed have a corresponding set of C# interfaces? How does one write to the browser window, get user input, network I/O, etc?
Unfortunately there is nothing available to expose Pepper interfaces directly to the managed environment that is shipped with this, though it is possible to auto generate bindings and glue code to make it work. What you'll see in the HelloWorld example I linked above is a very manual way of doing this, exposing an internal call that itself just calls directly through the C Pepper interface, effectively allowing Pepper calls from C#.
Re: Mono 3.2
#70Earlier quoted context omitted.
> Mono had full GTK support. And meagre QT support. > Tons of popular Gnome apps were written in Mono And very few KDE apps. > There was nothing "second-class citizen" about it. Except that it simply didn't belong to half the desktops (i.e. ones running KDE, which might actually account for more than half the deployed Linux desktops, considering it's long been the most popular Enterprise choice). > The same tech powe…
> And meagre QT support. So what? It targeted the Gnome desktop. Does it have to catter to every GUI toolkit there is? > And very few KDE apps. And no KDE app at all was written with GTK. So what? Mono developers targeted GNOME. > Except that it simply didn't belong to half the desktops (i.e. ones running KDE, which might actually account for more than half the deployed Linux desktops, considering it's long been the…
To be a first-class citizen on "the Linux desktop", covering at least both main alternatives is a must.
> Mono developers targeted GNOME.
Thereby renouncing half the desktops.
>Actually the most popular Enterprise choice has been Gnome for half a decade or more
Maybe in the States. In Europe, KDE has long been the most popular choice for large deployments, which is why RedHat and friends still ship it.