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

231–240 of 327 posts

Re: Announcing .NET Core 1.0

#231

Post by cpeth »

At my shop we have been using ASP Core since RC1 and have been quite happy with it. The tooling feels a lot like Node.js in a way, much different from any previous .NET development. It's awesome to have C# be deployable as docker containers on Linux hosts.

My biggest gripe so far has been that Nuget doesn't have a way to search only for libraries that are Core compatible.

If you are San Diego area and interested in working on Core, we are hiring. Inquire at christian.peth(at)millenniumhealth.com

Re: Announcing .NET Core 1.0

#232

Post by ickler9 »

WorldMaker wrote: post #149
yread wrote: post #136

Any ideas how to do GUI development with .NET Core? Is there a version of Xamarin? Are there plans to port Windows.Forms, WPF? There is this massive thread about it http://forums.dotnetfoundation.org/t/cross-platform-wpf/421/... and an issue here https://github.com/dotnet/corefx/issues/5766

Universal Windows Platform ".NET Native" stack is aligned with (built upon/merging towards) .NET Core. It's XAML-based like WPF and Silverlight. ETA: Other than not cross-platform. Other option is Xamarin.Forms and would be useful to see more Xamarin.Forms targets.

yea, xamarin.forms targets UWP.

and looks like there's a forms mac branch being somewhat worked on: https://github.com/xamarin/Xamarin.Forms/tree/mac

Re: Announcing .NET Core 1.0

#233

Post by Klathmon »

logfromblammo wrote: post #218
MichaelApproved wrote: post #150

Earlier quoted context omitted.

You're joking but I'll give a serious reply to why your analogy is off. This is why they have war games. The telemetry from those games would be included in the analysis.

My point was that user interface patterns do not always indicate the importance of the control, because there may be multiple modes of operation (such as "Standby", "War", "War Game", and "Readiness Drill") that might not be obvious--or even apparent--from the raw button-press numbers. You want the "War Game" telemetry to count for the "War" design, but you can't really tell which is which without having additional d…

But they aren't saying they will blindly follow the telemetry data, just that it's an important factor.

You need to determine which feature to add:

1. One that 3 developers asked for

2. One that 6 developers asked for.

With telemetry that can become:

1. One that 3 developers asked for and can improve things for 60% of your userbase.

2. One that 6 developers asked for, but only 12 of them are using the function that it will improve.

Without telemetry data, you are playing with an arm tied behind your back.

Re: Announcing .NET Core 1.0

#234

Post by michaeltyson »

4684499 wrote: post #176
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…

I simply don't want to be tracked in any form regardless of whether it collects my personal data. Yet it seems more and more impossible these days. It's like "If there's nothing about collecting your personal data, then you should compromise".

Sorry to tell you this 4684499, but this website and most every other website on the internet knows how many page views they have and the IP addresses that are used to get to their website, etc. ...all because they have telemetry on the server. It's how they tell if something is working or not working. Not all telemetry is bad.

Re: Announcing .NET Core 1.0

#235

Post by chrsstrm »

dd9990 wrote: post #172
pjmlp wrote: post #143

Earlier quoted context omitted.

So it is bad when Microsoft asks to do it, but ok when Eclipse, Netbeans or InteliJ do it? They are being quite open about it and how to turn it off.

Yes. It's bad when Microsoft does it this way because it's opt-out. IntelliJ/Android Studio prompts you and asks you your preference first. I think Eclipse is opt-in but could be mistaken.

Homebrew is opt-out post-install by setting a flag as well (no option or warning pre-install). But they do remind you afterwards that they are tracking and give you a link to learn how to disable it. As long as no data is sent until first use (giving you a buffer to opt-out), I don't have an issue with this.

Re: Announcing .NET Core 1.0

#236

Post by dingle_thunk »

jobigoud wrote: post #169
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.

> a button was removed from File Explorer Would that be the "Go up to the parent directory" button that was removed in 7 by any chance?

No. And that was added back in Windows 10.

Re: Announcing .NET Core 1.0

#237

Post by Retra »

pjmlp wrote: post #143
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 it is bad when Microsoft asks to do it, but ok when Eclipse, Netbeans or InteliJ do it? They are being quite open about it and how to turn it off.

Microsoft is a bit more influential than those guys, no?

Re: Announcing .NET Core 1.0

#238

Post by MagicWishMonkey »

computerlab wrote: post #24

A couple months ago I installed .NET core on a Ubuntu virtual machine running on the Windows 10 hypervisor, and was able to get a MVC5 app running using Visual Studio Code. As someone who really loves Visual Studio (it made me expect a lot more from my tools) and C# (it made me expect a lot more from my languages), it was an exciting moment. I actually took a selfie with my monitor. It was still a little rough: the "…

I wish MS would release a stripped down version of VS for OSX/Linux, but I know it probably won't happen.

Re: Announcing .NET Core 1.0

#239

Post by Retra »

4684499 wrote: post #176
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…

I simply don't want to be tracked in any form regardless of whether it collects my personal data. Yet it seems more and more impossible these days. It's like "If there's nothing about collecting your personal data, then you should compromise".

A router has to track you to know where to send the info you've requested.

Re: Announcing .NET Core 1.0

#240

Post by enricosada »

acangiano wrote: post #101
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.

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.

Bug was found too late, near code freeze for rtm, not enough time for fix.

fix is in progress ( https://github.com/Microsoft/visualfsharp/pull/1290 ) probably tomorrow, it's not a big problem one or two days of delay. Also because that's an sdk issue (preview2) not of .NET Core (rtm)

The f# support is in beta, c# was ahead obv, but that's ok i think, it's used as the language for the corefx, etc. vb is not working at all atm.

The .NET Core sdk preview1 worked ok ootb, see for example the https://github.com/SuaveIO/Suave-CoreCLR-sample working xplat (win/ubuntu/osx/docker). And the preview1 continue to work.

What i really like it's how the sdk it's evolving, using modularized components it's possibile to fix/improve/evolve the f# compiler/library, without waiting a new version of sdk. That's really good.

In the next sdk or rtm also the `dotnet new` it's going to be updatable, so np about template too

Post reply on HN