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

251–260 of 327 posts

Re: Announcing .NET Core 1.0

#251

Post by vgbm »

MagicWishMonkey wrote: post #248
Chlorus wrote: post #246

Earlier quoted context omitted.

Does this count? https://www.visualstudio.com/en-us/products/code-vs.aspx

I've played with VS Code a bit, it's a pretty cool tool for small scale scripting, but it's not really a replacement for a full fledged IDE. Hopefully Jetbrains will release their cross platform C# IDE sometime soon. I would prefer Visual Studio, but I don't think that's going to happen (at least not anytime soon).

From my experience, Rider is pretty stable and usable. Have you tried it out at all? https://www.jetbrains.com/rider/

Re: Announcing .NET Core 1.0

#252

Post by MagicWishMonkey »

vgbm wrote: post #251
MagicWishMonkey wrote: post #248

Earlier quoted context omitted.

I've played with VS Code a bit, it's a pretty cool tool for small scale scripting, but it's not really a replacement for a full fledged IDE. Hopefully Jetbrains will release their cross platform C# IDE sometime soon. I would prefer Visual Studio, but I don't think that's going to happen (at least not anytime soon).

From my experience, Rider is pretty stable and usable. Have you tried it out at all? https://www.jetbrains.com/rider/

Oh, didn't realize you could request early access. I'll check it out, thanks.

Re: Announcing .NET Core 1.0

#253

Post by carussell »

oblio wrote: post #192
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.

The source is MIT and Apache, but that doesn't mean the binaries you get from MS are redistributable.

For anyone asking this question and not getting a sufficient answer, the safe route would be "build from source, then distribute that".

Re: Announcing .NET Core 1.0

#254

Post by stephengillie »

jsingleton wrote: post #103
Analemma_ wrote: post #87

Earlier quoted context omitted.

I choose to ignore this post so five weeks from now I can write an outraged "Microsoft is TRACKING YOU" article on Medium that will garner me praise and upvotes.

Much quicker and easier than simply forking the code and commenting out the telemetry feature :P

And also generates more upvotes.

Re: Announcing .NET Core 1.0

#256

Post by tacos »

ATsch wrote: post #244
tacos wrote: post #202

Earlier quoted context omitted.

And 100x quicker than setting the clearly documented environment variable that disables the feature. > You can opt-out of the telemetry feature by setting an environment variable DOTNET_CLI_TELEMETRY_OPTOUT (e.g. export on OS X/Linux, set on Windows) to true (e.g. “true”, 1). Doing this will stop the collection process from running.

It is still opt-out, and thus considered harmful (at least by me)

"The telemetry is only in the tools and does not affect your app."

Re: Announcing .NET Core 1.0

#257

Post by spo81rty »

jenscow wrote: post #97
wvenable wrote: post #85

Earlier quoted context omitted.

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.

Like when they removed Macros from Visual Studio because according to telemetry only 1% of users used them.

I only remember accidentally t turning them on and they getting mad!

Re: Announcing .NET Core 1.0

#258

Post by newjersey »

ATsch wrote: post #244
tacos wrote: post #202

Earlier quoted context omitted.

And 100x quicker than setting the clearly documented environment variable that disables the feature. > You can opt-out of the telemetry feature by setting an environment variable DOTNET_CLI_TELEMETRY_OPTOUT (e.g. export on OS X/Linux, set on Windows) to true (e.g. “true”, 1). Doing this will stop the collection process from running.

It is still opt-out, and thus considered harmful (at least by me)

I'm one of the self-appointed resident whiners but I think I'll cut them some slack because they've used the magic word "preview".

This case is different from silently adding telemetry on a minor upgrade to a tool in production

Re: Announcing .NET Core 1.0

#259

Post by jsmeaton »

ATsch wrote: post #244
tacos wrote: post #202

Earlier quoted context omitted.

And 100x quicker than setting the clearly documented environment variable that disables the feature. > You can opt-out of the telemetry feature by setting an environment variable DOTNET_CLI_TELEMETRY_OPTOUT (e.g. export on OS X/Linux, set on Windows) to true (e.g. “true”, 1). Doing this will stop the collection process from running.

It is still opt-out, and thus considered harmful (at least by me)

I just installed these tools and it tells you on first invocation that telemetry is enabled and how ti disable it. I think that buys a little bit of good will. I am also opposed to telemetry by default, but I understand it, and appreciate the opt out message being presented clear and up front.

Re: Announcing .NET Core 1.0

#260

Post by hiram112 »

Microsoft is about 5 years too late with this.

I'm sure their MVC stack is fine, but this isn't a problem needing a solution in 2016. There are dozens are frameworks in your favorite language that can deal with taking HTTP requests, grabbing data from a backend, and spitting it out as JSON. They all run fine on Linux servers, are easy to develop on Mac.

C# is a nice language too, but I'd need a compelling reason to jump from Java / Scala over to .Net. And JetBrains puts out products just as good as Visual Studio for every major language.

The one thing that might make me consider this would be MS implementing the actual valuable part of .Net to Linux, Mac, and others: the desktop GUI libs and Visual Studio GUI tools.

Of course this will never happen since the MS dev tools team is beholden to the Office and OS departments.

Instead, I imagine .Net core will not gain much traction.

Post reply on HN