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

Building and Running .NET’s CoreCLR on OS X

praeclarum.org

Post reply on HN
Print view View original

51–59 of 59 posts

Re: Building and Running .NET’s CoreCLR on OS X

#51

Post by axefrog »

mdaniel wrote: post #41
ubertaco wrote: post #13

Earlier quoted context omitted.

As a POSIX-loving, open-source-breathing guy: platform availability being equal, why choose Java over C#?

I would venture it's a ton easier to find Java programmers than C# ones (at the current moment), and the same story for libraries for likely the same underlying reason. As a pragmatic issue, if you weren't already using Mono, then it would probably be wise to let the newly open-sourced CoreCLR stew for a while to find subtle kinks introduced by the process through which it was open-sourced and/or the pressures exerte…

Visual Studio + ReSharper. Hardly unfair.

Re: Building and Running .NET’s CoreCLR on OS X

#52

Post by MichaelGG »

praeclarum wrote: post #46
jbigelow76 wrote: post #43

Earlier quoted context omitted.

According to whom? And what is the current recommended GUI toolkit?

Windows RT (aka Metro, aka Store Apps). It's a model based on WPF but not fully compliant - it took in lessons learned form Silverlight. Call it WPFlight.

That's the toolkit if you want Metro apps, dealing with MS's crappy store, etc. etc. If you want a traditional Windows application that just works, then WPF is fine. (And I think WPF has an option for non-blurry text rendering, whereas every Metro app seems to be blurry.)

Re: Building and Running .NET’s CoreCLR on OS X

#53

Post by Razengan »

I just hope this doesn't reduce the overall quality of upcoming Mac apps.

Cocoa's AppKit is very powerful and provides a UI that has always been more consistent than what I've experienced on Windows. The last time I tried .Net/WinForms several years ago it was severely lacking in the functionality and flexibility of controls like tables and toolbars, and the UI of many Windows apps still tends to look and act slightly different from each other, with Microsoft being the biggest culprits in this inconsistency.

Re: Building and Running .NET’s CoreCLR on OS X

#54

Post by wluu »

Razengan wrote: post #53

I just hope this doesn't reduce the overall quality of upcoming Mac apps. Cocoa's AppKit is very powerful and provides a UI that has always been more consistent than what I've experienced on Windows. The last time I tried .Net/WinForms several years ago it was severely lacking in the functionality and flexibility of controls like tables and toolbars, and the UI of many Windows apps still tends to look and act slightl…

I think the focus of the CLR/.NET team at MS at this stage is on the server side (eg: ASP.NET).

So it's not going to suddenly open the floodgates of .NET apps running on a Mac. That's still a long long way away (if at all).

Re: Building and Running .NET’s CoreCLR on OS X

#55

Post by meddlepal »

ubertaco wrote: post #13
chii wrote: post #9

i wonder if other languages can start targeting the CLR, and have a competing cross platform runtime to java that's got a big name behind it.

As a POSIX-loving, open-source-breathing guy: platform availability being equal, why choose Java over C#?

Tooling and libraries. If JetBrains cranks out a .NET IDE then sign me up. I don't really want to learn Visual Studio. Also I develop on Linux primarily so VS isn't even an option.

Re: Building and Running .NET’s CoreCLR on OS X

#56

Post by stuaxo »

praeclarum wrote: post #40
sklogic wrote: post #34

Earlier quoted context omitted.

You can run Java on top of .NET and Mono easily, see iKVM.

In fact it runs quite well on .NET. My favorite demo is seeing how much faster Eclipse loads on the .NET runtime than the Java.

Does intellij / pycharm work ?

Re: Building and Running .NET’s CoreCLR on OS X

#57

Post by ttrashh »

mdaniel wrote: post #41
ubertaco wrote: post #13

Earlier quoted context omitted.

As a POSIX-loving, open-source-breathing guy: platform availability being equal, why choose Java over C#?

I would venture it's a ton easier to find Java programmers than C# ones (at the current moment), and the same story for libraries for likely the same underlying reason. As a pragmatic issue, if you weren't already using Mono, then it would probably be wise to let the newly open-sourced CoreCLR stew for a while to find subtle kinks introduced by the process through which it was open-sourced and/or the pressures exerte…

One of JetBrains primary products is Resharper. It's a must have add on for Visual Studio. If we're going to be subjective I'd say no other IDE gets close to the combination of Visual Studio and Resharper.

Re: Building and Running .NET’s CoreCLR on OS X

#58

Post by will_hughes »

jbigelow76 wrote: post #28
adolfojp wrote: post #18

Earlier quoted context omitted.

Cross platform .NET usually means using a native toolkit on each different platform and the result is WPF on Windows, GTK# on Linux, and MonoMac on Mac. The purpose of this is to avoid the uncanny valley of cross platform toolkits like Java Swing at the expense of writing extra UI code. Some wrappers like Eto.Forms and XWT exist but don't expect drag and drop visual designer tooling. Thanks to Mono WinForms is sort o…

>Cross platform .NET usually means using a native toolkit on each different platform and the result is WPF on Windows, GTK# on Linux, and MonoMac on Mac. What are the odds Microsoft announces WPF open sourcing and maybe a wrapper of some sorts for OSX support at Build this year? I give it at least 50/50 on the open sourcing part.

WPF is very heavily tied into DirectX and other Windows-only APIs.

Open Sourcing it is one thing, converting that into an engine that can do layout and rendering identically across multiple platforms is non-trivially difficult. Talk to the browser folks on how hard they had to work on that, and they wern't dealing with 3D stuff.

Re: Building and Running .NET’s CoreCLR on OS X

#59

Post by derefr »

I was expecting a "complete bootstrap", but even after the end of this article you're still using Mono to compile any further executables you want to run on CoreCLR, right?

I guess what I'm asking is, where's the open-source MSVS C# compiler core+build system+CLI tooling?

Post reply on HN