Live data from Hacker News

Mono 3.2

mono-project.com

51–60 of 70 posts

Re: Mono 3.2

#51
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 directions I think they should come out and say it so current and potential future users of the platform know.

Re: Mono 3.2

#52
post #5

Earlier quoted context omitted.

How is Mono not platform independent? It doesn't have a lot of .net features from Windows like windows forms, but it has the entire C# language and their own implementations of xna, etc. The only concern I would have is that Microsoft might try to crush Xamarin at some point, but I wouldn't count that likely, Mono is their ticket to keep .net from looking like anti-competitive platform lock in.

Mono is Windows encroachment onto nix. It's a square peg forced into a round hole. It's trying to force fit its tools, something that works good for Windows, onto nix but *nix tools are superior in every way. I wish I could go on but I've had this argument before.

Mono is tolerated by Microsoft, and supported behind the scenes (not financially or anything, more like cheerleading) because it lets MSFT tell enterprise customers that "See: You aren't locked into Windows - there's a Linux alternative that you could use."

Microsoft is not setting technical direction for Mono, and I expect that there are few (if any) Microsoft employees contributing to the project -- because of conflict of interest and IP concerns. They are very much at arms-length with regards to Mono.

So far as *nix tools being superior - I would agree that they do what they are designed to very well. But don't turn up your nose at C# and the .net framework -- it's quite good, and doesn't have the Java factory factory factory issues.

Re: Mono 3.2

#53
post #20

Earlier quoted context omitted.

I wish someone would package this version of Mono for Debian Testing (or at least Sid). I am starting to love building things from source, but having no official documentation on how to build Mono/MonoDevelop from source the correct way really is tiring. (Installing pango/gtk etc from source really takes the juice out of you.)

http://www.mono-project.com/Compiling_Mono First result on Google for building Mono. Download the source, unpack, configure, make install. I've done this on many versions, and it seems to work just fine.

Sorry, I should have been more clear. Installing Mono from Git is quite straightforward. Whereas for MonoDevelop, I found its not that simple, at least for me. Installing dependency after dependency especially while building GtkSharp, pango has not been successful for me, yet.

I go at it every few weeks with renewed interest, but at some point I find myself wading through the forums where there is little or no response to questions similar to the ones I have at that moment.

Re: Mono 3.2

#54
Please someone release an Ubuntu 12.x package for this. I was using Meebey's PPA for 3.0 but it hasn't been updated in a while.

Re: Mono 3.2

#55
post #33

Earlier quoted context omitted.

That all said, Unity's version of Mono is pretty old, kind of crippled in annoying ways, and they're using an old, buggy version of MonoDevelop (which can't even be bothered to pick up my Xamarin Studio code formatting settings). It's extremely rough going and pretty unpleasant to work with, IMO, to the point where I've gone to a home-rolled C++ engine for my project (having originally come from XNA, tried and ruled…

Have you tried Visual Studio? It's an amazing IDE to work with when building games in Unity

Well, yeah. I've used it, and if you're using Unity, it's the only serious option. It's still terrible, because it tweaks out ReSharper (for very good reasons on ReSharper's part--Unity thinks dumping everything in one namespace is a good idea and all sorts of stuff breaks otherwise) and because there's no real support for the dog-stupid not-actually-JavaScript that you're forced to contend with because so much existing code uses it.

Re: Mono 3.2

#56
post #7
post #5

Earlier quoted context omitted.

How is Mono not platform independent? It doesn't have a lot of .net features from Windows like windows forms, but it has the entire C# language and their own implementations of xna, etc. The only concern I would have is that Microsoft might try to crush Xamarin at some point, but I wouldn't count that likely, Mono is their ticket to keep .net from looking like anti-competitive platform lock in.

Because the all the main frameworks asp.net MVC, entity framework tend to be a bit flaky using mono. The up to date versions may not work.

So, which platform independent kit do you use where every framework is kept perfectly up to date for every platform?

Re: Mono 3.2

#57
post #41
post #29

Earlier quoted context omitted.

> That's a wild generalization which I don't think it's true. The "Linux community" you speak of is a loud minority of mentally deranged folks. Ironic, because then you go to state: > Mono never succeeded on Linux because it always felt like a second-class citizen on the desktop Mono had full GTK support. Tons of popular Gnome apps were written in Mono, music apps, photo viewers, desktop search etc. There was nothing…

> 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 most popular Enterprise choice).

Actually the most popular Enterprise choice has been Gnome for half a decade or more. The only major exception had been SuSE, a distro which languished. RedHat (and Centos), Ubuntu, etc all went for Gnome.

Re: Mono 3.2

#58
post #45
post #27

Earlier quoted context omitted.

> 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.

Vala is an incredible project. With a relatively small number of contributors, it's turned into an easy language to work with, that can compile into shared libraries with automatic bindings for Python, Ruby, Lua, etc., and get near C performance. GTK bindings are pretty complete. With some effort (I hear -- never tried it), it can even run on Windows and OSX. Vala may be one of the most underrated Linux projects arou…

Vala looks interesting.

It would appear that with GTK libraries available on Windows and OSX, a port of a Vala app should be trivial. Valac compiles to C and then GCC takes over for the rest of it.

It seems like the most well-known Vala apps are managed in San Francisco by Yorba, however they're only for Linux. http://www.yorba.org/projects/

Any examples of cross-platform apps written in Vala?

Re: Mono 3.2

#60

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.
Post reply on HN