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

Announcing .NET Core 1.0

blogs.msdn.microsoft.com

Post reply on HN
Print view View original

191–200 of 327 posts

Re: Announcing .NET Core 1.0

#191

Post by Alupis »

Practicality wrote: post #187
bigtones wrote: post #20

Earlier quoted context omitted.

.Net is 14 years old now - if you don't know what it is by now you're probably not ever going to know. It's a cross platform runtime and a group of programming languages that run on it, just like Java.

Java is confusing too so being just like Java doesn't mean it's easy to understand. (Do I need the Java runtime environment, the SDK or the browser extensions to run this code?)

> Java is confusing too

> Do I need the Java runtime environment, the SDK or the browser extensions to run this code?

It's not really confusing.

The Runtime is required to run code. The Source Development Kit (SDK) is for development, and the Browser Extension is for running browser extensions.

Re: Announcing .NET Core 1.0

#192

Post by oblio »

mikevm wrote: post #180

What is the licensing like if you're a vendor and you want to ship software based on .NET Core on your own hardware appliances? Can you redistribute the runtime, or do you have to pay?

MIT and Apache, apparently.

Re: Announcing .NET Core 1.0

#193

Post by hackaflocka »

Is there a primer somewhere that explains simply what the difference and dependence is between .NET (core, foundation), ASP.NET (core, foundation), Xamarin, Visual Studio (in all it's different flavors including VS.NET etc.) and Visual Studio Code?

I tried Wikipedia, and Microsoft's own homepages for each, and am even more confused.

I'm a hierarchical thinker, and a hierarchical tree explaining the above would be very very helpful.

Disclaimer: I haven't downloaded any of these yet. I usually don't until I've understood something.

Bonus question: If I want to develop websites and electron apps using: HTML, CSS, Javascript and PHP, what's the minimum set of technologies (or whatever it is that Microsoft is calling them these days) I will need?

Re: Announcing .NET Core 1.0

#194

Post by jongalloway2 »

616c wrote: post #120
daveguy wrote: post #67

FYI, from the announcement. Probably the most important part at the end, italicized by me. Also note (elsewhere) that licenses are MIT and Apache2: .NET Core Tools Telemetry The .NET Core tools include a telemetry feature so that we can collect usage information about the .NET Core Tools. It’s important that we understand how the tools are being used so that we can improve them. Part of the reason the tools are in Pr…

So random question: I like when MS people come out and engage the community like we are responsible adults and not like moronic children who need hand-holding and cannot decide for ourselves. Since we all know the famous "Open Source is cancer" reign of Balmer oft-joked of here, I assume the related issue at hand is culture shift is good and less of a concern now, as opposed to a few years ago. But I am super happy w…

The best way to make sure they (we, since I work at Microsoft) get the feedback is by finding out where the product is listening.

A lot of products have UserVoice set up, a lot of dev product teams (dotnet, asp.net, etc.) are looking for GitHub issues.

For Windows 10 I'd recommend using the Windows 10 Feedback Hub - if you hate something about Windows 10, post feedback in the Feedback Hub before you uninstall it.

Visual Studio has this page that explains where best to submit feedback / bugs / feature requests: https://msdn.microsoft.com/en-us/library/b8akas30.aspx

There are lots of us who see your comments on HN / Reddit / Slashdot / etc. but having been part of the Microsoft ecosystem (both inside and out of Microsoft) for many years, I can tell you that there's a huge difference between "I've seen some unhappy comments about X" and "Our feedback numbers show 68% of users want us to improve feature X". Also, specifics are important - a detailed issue report with repro steps and recommendations for what you'd like to see work a whole lot better than "@drunkvs LOL VS suxxxx ikr!!!"

Also, just because I'm an ocd fact checker, Ballmer technically didn't say "open source is a cancer". He said that Linux is a cancer, referring to the strong copyleft license requirements (https://web.archive.org/web/20011211130654/http://www.suntim...). [yes, I very well know that you can run software on Linux without that software being GPL. I'm writing this from Red Hat DevNation :)]

Regardless, I can tell you that our current CEO and everyone I work with is excited about writing great software that runs everywhere.

Re: Announcing .NET Core 1.0

#195

Post by kbenson »

emn13 wrote: post #165
hatchnyc wrote: post #104

Earlier quoted context omitted.

I always suspected that there was probably significant overlap between users of macros and users who opted out of telemetry. Lesson learned: leaving "yes" checked from now on.

Big Brother has trained you well. ;-)

Yep. Don't vote and nobody will care about your (unexpressed) needs when making decisions.

Re: Announcing .NET Core 1.0

#196

Post by hurricaneSlider »

enricosada wrote: post #41

F# doesnt work ootb with sdk preview2. Work ok with preview1 of SDK (win/ubuntu/osx/docker), but preview2 has a bug, the fix is in progress ( ref https://github.com/dotnet/netcorecli-fsc/issues/12 ) and will be published a nuget package with fix soon.

Odd it worked for me without any problems

Re: Announcing .NET Core 1.0

#197

Post by jongalloway2 »

soundoflight wrote: post #108
computerlab wrote: post #79

Earlier quoted context omitted.

Good point, I meant MVC6. I confused the versions of ASP.NET 5 (which is now known as ASP.NET Core) and MVC6.

MVC 6's name is now also ASP.NET Core MVC 1.x.x. It's really a version number reset. The confusing thing is that it's not plugged through everywhere and people interchange the two regularly.

#wellactually We don't talk about ASP.NET MVC as a separate thing anymore. It's just ASP.NET Core. So you might build an MVC app on ASP.NET Core, or build APIs on ASP.NET Core, etc., but it's all just ASP.NET Core.

Re: Announcing .NET Core 1.0

#198

Post by edgyswingset »

ngrilly wrote: post #154

A few years ago, I wouldn't have thought I would write this, but it looks like Microsoft is definitely changing, for the best! Two questions: - Does .NET Core offers something similar to Go goroutines or Erlang "lightweight" processes? - And something similar to gofmt?

> Does .NET Core offers something similar to Go goroutines or Erlang "lightweight" processes?

Not quite the same thing, but F# has the MailboxProcessor type which is conceptually similar to Erlang processes and can be used in the same way.

Re: Announcing .NET Core 1.0

#199

Post by luciusism »

wvenable wrote: post #85
daveguy wrote: post #67

FYI, from the announcement. Probably the most important part at the end, italicized by me. Also note (elsewhere) that licenses are MIT and Apache2: .NET Core Tools Telemetry The .NET Core tools include a telemetry feature so that we can collect usage information about the .NET Core Tools. It’s important that we understand how the tools are being used so that we can improve them. Part of the reason the tools are in Pr…

Microsoft is looking to do more data-driven design; this is the reason for all the telemetry in Windows as well. Raymond Chen pointed out an example where a button was removed File Explorer (prime real-estate) because the telemetry showed that hardly anyone ever pressed it. It's unfortunate they are so tone-deaf about the PR implications in Windows.

The "Compatibility Files" button was removed: https://blogs.msdn.microsoft.com/oldnewthing/20150902-00/?p=...

Re: Announcing .NET Core 1.0

#200

Post by eperfa »

I might be missing something here, but does this mean that .NET Framework and .NET Core have diverged, and you need to take extra steps to keep code compatible with both?

The major differences between .NET Core and the .NET Framework: [...] APIs — .NET Core contains many of the same, but fewer, APIs as the .NET Framework, and with a different factoring (assembly names are different; type shape differs in key cases). These differences currently typically require changes to port source to .NET Core.

While I understand the motivation, this at first sight looks like something that will be with us for a long time, and could make life more difficult especially for library authors, who need to potentially target both 'platforms'.

[Disclaimer: haven't used .NET technologies for a very long time and might be horribly wrong here]

Post reply on HN