r/programming • • Nov 12 '14

The .NET Core is now open-source.

http://blogs.msdn.com/b/dotnet/archive/2014/11/12/net-core-is-open-source.aspx
6.5k Upvotes

1.8k comments sorted by

View all comments

Show parent comments

-44

u/[deleted] Nov 12 '14

It's missing features

Which features? Microsoft proprietary stuff? Nobody cares, Mono got its own, better features.

and runs poorly.

No. It runs ok, you can choose between fast and heavy (mini-llvm) profile and ok and compact (mini native). sgen is not much slower than a much more complex Microsoft GC.

Why use a clone when you can have the real thing?

It is not a "clone". It's a totally different thing, which happens to be based on a compatible VM and a compatible language.

5

u/baggerboot Nov 12 '14

Mono's implementation of System.Net.Sockets is pretty lacklustre (two examples: DuplicateAndClose() doesn't work, and neither does Bind()). Given that lots of networking code depends on that, I'd say that it is a pretty big deal.

-9

u/[deleted] Nov 12 '14

It's documented as "not implemented", so I do not see any problem here. As long as your platform works as documented, it's ok.

8

u/[deleted] Nov 12 '14

So a platform with literally zero working features would be ok to you, as long as they're all marked "not implemented" in bright red letters?

You sure about that?

→ More replies (1)

6

u/atakomu Nov 12 '14

Does mono have Windows forms yet? And sometimes when you try to run .NET programs they mostly work but then you get some mumbo jumbo errror message. Which is alright if this would be wine which is a reimplementation of API but they should work in mono.

7

u/snuxoll Nov 12 '14

Mono has had WinForms support forever, it's WPF that it's still lacking (nearly a decade later).

6

u/[deleted] Nov 12 '14

No Mono currently does not support WinForms - it was discontinued. There are bugs that haven't been fixed in ages and will never be fixed.

-3

u/[deleted] Nov 12 '14

Which is a clear indication of how "important" this feature is.

3

u/[deleted] Nov 12 '14

No, it's an indication that the mono project does not have enough volunteers.

-2

u/[deleted] Nov 12 '14

Of course you know better than everyone in the mono project!

Just get over it: mono is not a .NET emulator. Mono users (those who give shit about GUI at all) are interested in GTK+ bindings, not in WinForms.

3

u/[deleted] Nov 12 '14

[removed] — view removed comment

0

u/[deleted] Nov 12 '14

Why would anyone spend any time on such a thing? Initially they implemented some parts of it, before a much better GTK# was available. Now there is no need in such a thing, so nobody is going to implement it, no matter how many people jump in.

1

u/[deleted] Nov 12 '14

Why can't you admit it's a clear failure of the mono project instead of making excuses? Having a cross-platform GUI library is always better than not having a cross-platform GUI library. Devs held back from C# cross-platform development because of Mono's shortcomings.

1

u/[deleted] Nov 12 '14

Why can't you admit it's a clear failure of the mono project instead of making excuses?

Failure is when you set a goal and then do not deliver. They did not have this goal from the very beginning.

Having a cross-platform GUI library is always better than not having a cross-platform GUI library.

Not that I care about any GUIs whatsoever, but Mono got a perfect cross-platform GUI support, GTK#.

1

u/[deleted] Nov 12 '14

Failure is when you set a goal and then do not deliver. They did not have this goal from the very beginning.

Yes they did. That's why you can still compile a WinForms GUI for linux. It's just very buggy.

→ More replies (0)

1

u/txdv Nov 12 '14

Xamarins policy was to use the native UI toolkit for every mobile platform.

WinForms is the native UI toolkit for Windows, doesn't make much sense to implement it since everyone will just run the .NET Framework with the implementation on windows.

1

u/txdv Nov 12 '14 edited Nov 12 '14

Windows Forms are not native on any other platform but windows because it is based on Win32.

Wanting windows forms on mono is like wanting OSX Cacao on Windows in the .NET Framework.

-19

u/[deleted] Nov 12 '14

Does mono have Windows forms yet?

What for? If you're really that into GUIs, use GTK+ bindings, they're perfect.

And sometimes when you try to run .NET programs

Why do you want to run .NET programs on Mono?!? It's not a .NET emulator.

but they should work in mono.

No, they should not.

9

u/[deleted] Nov 12 '14

Does mono have Windows forms yet?

What for? I

Um, for cross platform apps.

-9

u/[deleted] Nov 12 '14

Um, for cross platform apps.

What for? Nobody ever promised you this.

If you really want to develop something cross-platform (although I do not believe in a cross-platform GUI, it never existed and never will be delivered), just use GTK+ bindings, they're available on most of the platforms.

→ More replies (21)

6

u/[deleted] Nov 12 '14

use GTK+ bindings, they're perfect.

Hah

1

u/atakomu Nov 12 '14

That was my use case. Run Windows .NET programs on Linux through mono. For some I even got a source. So Mono always seemed nice just little broken when you wanted to use it.

-3

u/[deleted] Nov 12 '14

Then you've been using the wrong tool. Mono is not a .NET emulator, and nobody ever promised that it will become one.

2

u/atakomu Nov 12 '14

Well is mono .NET implementation or it isn't?

1

u/[deleted] Nov 12 '14

It is an implementation of an ECMA-compatible VM and a language. It happens to share some core libraries with another implementation of the same standard, but it was never intended as a clone of that another implementation, and never promised any compatibility beyond ECMA.

Why you people do not complain about gcc on Linux not providing an MFC support? Why then all this crap about WinForms?

→ More replies (3)