Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mono 4.0.0 Release Notes

mono-project.com

Post reply on HN
Print view View original

41–50 of 63 posts

Re: Mono 4.0.0 Release Notes

#41

Post by coldtea »

azakai wrote: post #17
ComputerGuru wrote: post #2

And with this release we see the beginning of the convergence of the Mono and Microsoft codebases. I'm glad Mono will be more reliable as a result, there have always been persistent reliability and compatibility issues that the Mono team hasn't been able to really fix. It's also a little sad, in a way. It relegates Xamarin to maintainers of a distribution for another operating system. At the end of the day, C# and .N…

> It's also a little sad, in a way. It relegates Xamarin to maintainers of a distribution for another operating system. I'm not sure I understand what you mean here. As I understand things, Mono is still keeping its runtime - JIT, garbage collector (the release notes here mention optimizations to SGen), etc. That means Mono isn't nor is it planning to be "just" a distro for Microsoft's .NET. (But it is using more and…

>I'm not sure I understand what you mean here. As I understand things, Mono is still keeping its runtime - JIT, garbage collector (the release notes here mention optimizations to SGen), etc.

So? Who will still use those, if there's a fully supported MS based (+ some open source effort for some edges) alternative?

Re: Mono 4.0.0 Release Notes

#42

Post by coldtea »

nickysielicki wrote: post #21
ComputerGuru wrote: post #2

And with this release we see the beginning of the convergence of the Mono and Microsoft codebases. I'm glad Mono will be more reliable as a result, there have always been persistent reliability and compatibility issues that the Mono team hasn't been able to really fix. It's also a little sad, in a way. It relegates Xamarin to maintainers of a distribution for another operating system. At the end of the day, C# and .N…

> At the end of the day, C# and .NET are now officially first class citizens on Linux. C# and .NET will never be first class citizens on unix. This is by design. http://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish

That's a 15+ years off slogan from the Desktop/Browser wars era...

Nowhere near as relevant or enlightening as you think it is in 2015 (wasn't much of an analysis in 1998 either, but still...)

Re: Mono 4.0.0 Release Notes

#44

Post by smosher_ »

tacos wrote: post #4
ComputerGuru wrote: post #2

And with this release we see the beginning of the convergence of the Mono and Microsoft codebases. I'm glad Mono will be more reliable as a result, there have always been persistent reliability and compatibility issues that the Mono team hasn't been able to really fix. It's also a little sad, in a way. It relegates Xamarin to maintainers of a distribution for another operating system. At the end of the day, C# and .N…

The Mono team did an amazing job, and they actually had a lot of support deep within Microsoft all along. But yeah, I think it's okay to say "it never really worked." (And there's nothing wrong with being a port factory that deals with obscure path issues all day. That's why they give you a paycheck...) Still, Xamarin is doing a LOT more than just Mono, much of it extraordinary. Also delivering something that actuall…

> But yeah, I think it's okay to say "it never really worked."

I don't. I mean yes mono <4.0 has a lot of problems, but it works well enough for me to shell out money for applications running on mono and be happy about it.

Re: Mono 4.0.0 Release Notes

#45

Post by lhenry »

golergka wrote: post #40
azakai wrote: post #29

Earlier quoted context omitted.

Unity is moving away from Mono anyhow, http://blogs.unity3d.com/2014/05/20/the-future-of-scripting-... so updates in Mono are irrelevant to Unity.

What? That's what this post says: > we will also be upgrading to recent versions of the Mono C# compiler, base class libraries, and runtime for use in the editor > We will continue to use the Mono C# compiler (and perhaps later, Roslyn). We will continue to use the Mono class libraries. All currently supported features and 3rd party libraries which work with Mono AOT should continue to work with IL2CPP. We are only s…

They are (apparently) using Mono (C# compiler + base class libraries + runtime) on the desktop for their IDE, and they are using IL2CPP and parts of Mono (C# compiler + base class libraries, but not the runtime) on their targets (iOS, Android, ...)

Re: Mono 4.0.0 Release Notes

#46

Post by tacos »

smosher_ wrote: post #44
tacos wrote: post #4

Earlier quoted context omitted.

The Mono team did an amazing job, and they actually had a lot of support deep within Microsoft all along. But yeah, I think it's okay to say "it never really worked." (And there's nothing wrong with being a port factory that deals with obscure path issues all day. That's why they give you a paycheck...) Still, Xamarin is doing a LOT more than just Mono, much of it extraordinary. Also delivering something that actuall…

> But yeah, I think it's okay to say "it never really worked." I don't. I mean yes mono <4.0 has a lot of problems, but it works well enough for me to shell out money for applications running on mono and be happy about it.

I literally saved two businesses as favors to friends. One by replacing a Mono app on Mac with Windows running in a VM. The second by doing the two hours of config work they were afraid of to host on Windows Server instead of a Linux box. (At the same damn price!)

Xamarin did an immense amount of work pushing that boulder up a hill. Glad you got results, but frankly it did a lot of damage to a lot of people. I say this as a Microsoft fanboy and someone who deployed sites you've heard of on Mono + Postgres + CentOS.

In the last year or two many .NET vendors went from "yes, it works on Mono!" to "it should work but no support." This indicates the formal death of the ecosystem to anyone but apologist hobbyists and thankfully we've gotten to a better place now.

Re: Mono 4.0.0 Release Notes

#48

Post by migueldeicaza »

rajeevk wrote: post #10

Just curious.. Why cant the mono team replaces almost whole of their codebase with the code Microsoft open sourced? Is there anything stopping them to do that? Maybe licensing issues?

We are working on replacing those parts that we can.

But there are several issues:

* reference source code not being portable and not working on Unix. * complex dependencies between the portable and non portable pieces * some bits were only released recently, and without those it was not possible to port other chunks * dynamic happy code high prevents some code from being adopted as Mono can be used as a full static compiler on iOS, Xbox and Playstation.

So as time permits we will bring those over.

We also plan on supporting the "core" model where our contributions will flow back upstream.

But "core" is still a bit undefined

Re: Mono 4.0.0 Release Notes

#49

Post by needusername »

azakai wrote: post #29
thurn wrote: post #7

I look forward to being able to use this all in Unity3D in 7 years.

Unity is moving away from Mono anyhow, http://blogs.unity3d.com/2014/05/20/the-future-of-scripting-... so updates in Mono are irrelevant to Unity.

> Unity is moving away from Mono anyhow,

I don't know man. Mono moved away from Boehm GC to a real gc (SGen) because it never really worked for them bespite feeding it a lot of metadata. Others before them have found out that tanspiling to C/C++ isn't really that great (some of the more recent ones where HipHop PHP).

Re: Mono 4.0.0 Release Notes

#50

Post by tizoc »

migueldeicaza wrote: post #47

It is a shame that this got submitted before we actually published the code. It is Easter and many of our engineers are taking these days off. The release notes are also incomplete and not ready for publishing Miguel

Sorry, saw it on reddit as "Mono 4 Released"[1] and reposted here, without noticing it was just a draft (the "THIS IS A DRAFT" comment wasn't there at the moment).

[1] http://www.reddit.com/r/programming/comments/31ezp0/mono_4_r...

Post reply on HN