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

201–210 of 327 posts

Re: Announcing .NET Core 1.0

#201

Post by djsumdog »

georgemcbay wrote: post #133
logfromblammo wrote: post #106

Earlier quoted context omitted.

We have removed all the weapon deployment buttons from our nuclear subs, silos, and bombers, because telemetry shows that they are typically only pressed during unit testing. Since we only have two recorded events of someone deploying a nuclear weapon in a real-world scenario, it should be safe to relocate those buttons off the main console, and just use the auxiliary functions button, behind the kick panel, next to…

I know this is just meant in jest, but because the weapon deployment buttons are something you never want to be pressed on accident, ideally you really do want to obscure them behind layers and layers of user interaction. If anything we had the problem of them not being obscured enough for a while (if the story of the launch codes being 00000000 across the board is true).

I thought it was just four zeros (0000)

Re: Announcing .NET Core 1.0

#202

Post by tacos »

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 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.

Re: Announcing .NET Core 1.0

#203

Post by aweb »

Pharylon wrote: post #181
SoapSeller wrote: post #43

It's fascinating how Microsoft's marketing moved from ".Net - One platform with multiple languages" to "This is .Net - here some samples in C#"(without mentioning C# by name anywhere in the page). I think that .Net would be much better if they had this kind of focus in dev side from the start. *Hides from the f# mafia.

Can you make a mafia with only three people?

Funny, I saw far more than 3 F# presenters at NDC Oslo a few weeks ago..

Re: Announcing .NET Core 1.0

#204

Post by int_19h »

ramenmeal wrote: post #76
osullivj wrote: post #30

Earlier quoted context omitted.

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).

Re: Announcing .NET Core 1.0

#205

Post by jsingleton »

jongalloway2 wrote: post #197
soundoflight wrote: post #108

Earlier quoted context omitted.

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.

Personally, I like the new "one true name". However, most .NET developers know what ASP.NET MVC is for, but are less clear about what ASP.NET Core is about. Hopefully this will change over time but, for now at least, MVC is still a useful term from a marketing perspective, or at least that's what my publishers tell me. :)

Re: Announcing .NET Core 1.0

#207

Post by mattmanser »

dimgl wrote: post #178
mantenpanther wrote: post #132

I've mixed feelings about this release, because it seems a bit early to me. Some fundamentals will change soon (project.json replacement) and I am still not able to get debugging to work in VS Code on OSX. The whole situation in the .NET Core space was very confusing for the last months and this trend seems to continue. This is sad, because I'd love to code in C# on any platform and that things would just work as adv…

It's still extremely buggy. Very difficult to get a .NET MVC app up and running (they're not using the term WebAPI anymore).

I also think they've made a terrible decision, the first-class support for DI is a bad direction which has made many simple concepts like config settings into absolute farces that take 5 lines of code.

It's code "purity" over usability. It's putting the core dev team's principles over their customers actual need, completely violating KISS, DRY and YAGNI.

DI really is our generation's factories. I'm already seeing projects written by people who don't understand it making utter nightmare spagetti code, worse than any code I've ever seen.

It's nasty scaffolding code which is a symptom of limitations of the language, definitely not code anyone should ever actually be wasting time writing.

Instead of recognising it's a flash in the pan, the core team have embraced it and are trying to force it down everyone's necks, and a lot programmers simply don't get it and are making an utter mess instead.

Re: Announcing .NET Core 1.0

#208

Post by BHSPitMonkey »

kbenson wrote: post #195
emn13 wrote: post #165

Earlier quoted context omitted.

Big Brother has trained you well. ;-)

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

Well, it would be nice if there is a way to vote or express one's needs via some alternative to having one's usage actively mined for data.

Re: Announcing .NET Core 1.0

#209

Post by Eyas »

ubertaco wrote: post #129
acangiano wrote: post #101

Earlier quoted context omitted.

You reported the issue 11 days ago. I'm surprised they just announced it with such a basic use case being broken. It doesn't bode well for F# as a first class citizen in their ecosystem.

Seconded. I saw the announcement and immediately went to grab the docker image and give it a shot with F# via "dotnet new -l F#" and go. It restored and built, but didn't run. So v1.0 is broken, I guess?

I don't think so. It means that the tooling is broken, which is not at 1.0 yet (still in `preview2` I believe).

Re: Announcing .NET Core 1.0

#210

Post by michaelmior »

bad_user wrote: post #48

I don't understand, why does the package name for Linux say preview2? apt-get install dotnet-dev-1.0.0-preview2-003121 Isn't this the final release?

Even if this isn't the final release, I'm confused why they would include version numbers in the package name at all. One of the reasons of having a package manager in the first place is to avoid things like this.
Post reply on HN