Comment by judah | Hacker News Reader

Comment by judah | Hacker News Reader

Parent Full thread

It's the first version of .NET that's cross-platform, it's the first version of .NET that's totally open source, and it's the first version of .NET that can build self-contained apps (no need to have .NET Framework installed to run .NET Core 1.0 apps). See the release notes[0] for more info.

It's called "core", because it doesn't contain the Windows desktop UI toolkits, like Windows Forms and Windows Presentation Foundation (WPF), and excludes some other Windows-specific functionality.

Additionally, this is the first version of .NET in which apps can be totally self-contained. Previously, you'd need to install the .NET Framework on your machine to run .NET apps. That is no longer a requirement in .NET Core 1.0.

So, it's a pretty huge release. And really the first time in decades that MS has built it's premier dev stack with multiple OS support.

[0]: https://github.com/dotnet/core/blob/master/release-notes/1.0...

>>> it's the first version of .NET that can build self-contained apps

I tried it - it puts 50MB of DLLs beside the "HelloWorld" executable in a subdirectory (on Ubuntu 16.04).

It's like shipping the entire Java runtime with every app.

>> "I tried it - it puts 50MB of DLLs beside HelloWorld"

That's a bad test for a framework. It's like saying, "I bought an $80,000 car to drive to my neighbor's house across the street - I could have just walked!"

A good test is, "What is the full install size of a real app built on .NET Core?"

And the answer is, not much larger than any other app. All that code has to live somewhere, either in your app or in your libraries.

well, people complained when Go produced 2mb hello worlds.

Interesting. I'm guessing it doesn't support COM interop?

If you need COM interop, you don't need cross platform compatibility. You can just use the full .Net framework.

Mono supports COM interop on Linux, too. At its most basic level, COM is really just an ABI, and there's nothing Windows-specific about it (see also: XPCOM).

I remember working with COM on MacOS 8... And it supported remote objects, so, it'd be, in theory, possible to self inflict that pain.

I experience a physical revulsion just thinking about all the wasted years I spent with COM and DCOM.

https://docs.microsoft.com/en-us/dotnet/core/api/system.runt...

Though I'm not sure it's of any value outside of Windows.

Probably, and it should be considered a feature.

Reply on news.ycombinator.com