Live data from Hacker News

Announcing .NET Core 1.0

blogs.msdn.microsoft.com

211–220 of 327 posts

Re: Announcing .NET Core 1.0

#211

Earlier quoted context omitted.

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

Easily my favorite button in file explorer.

They still have that button, and you can go up by clicking on the parent folder name as well.

Re: Announcing .NET Core 1.0

#212
post #200

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

There are new platform targets that cover the common functionality. Support in NuGet is a bit nascent though.

https://github.com/dotnet/corefx/blob/master/Documentation/a...

Re: Announcing .NET Core 1.0

#213
post #137

Earlier quoted context omitted.

I think that kind of engagement is present on their github repos.

Well, until it is not interesting for them as a PR strategy. I do not want to lose these people when the pendulum swings back the other way. And you and I check Github. That does not mean anyone being engineering managers care. I am curious what else we can do beyond starring GH repos. I do that, I just do not like my lazy armchair form of support and worry I will lose a culture shift at MS I have quickly fallen in l…

Purely subjective and observational... but I had a few MS guys go out of their way to communicate a bug in probably the most popular node.js driver for MS-SQL (tedious), and it was interesting... There wasn't as much updated on the Github issue, but I was included in on some of the communication issues, and they were pretty open about it.

The person that had poked in was iirc, and Azure developer in MS, not from the MS-SQL team. There are plenty of developers at MS that do follow various GH projects (as happens everywhere else) and will get the right people involved when they see things.

I would presume that by pushing these kinds of projects (.Net Core, etc) out to github, and even the documentation likely won't see things close off any time soon, and not without losing more mindshare than Oracle has caused people to move away from Java.

Re: Announcing .NET Core 1.0

#214

Earlier quoted context omitted.

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.

There is mining for data and there is mining for data.

Monitoring which features I use? Opt in.

Monitoring what I do? Uninstall if possible.

Re: Announcing .NET Core 1.0

#215

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.

My point is that it's just hard to understand what exactly one means when they're writing ".Net". Do they mean the entire framework, a specific library, the CLR, one language, etc. For whatever reason, the name has a very contextual meaning, and people use them interchangeably (".Net Core" is clearly specific though). Not that they're alone. Adobe did worse with "Flex" since it could refer to the compiler, a framewor…

Java JRE/SE/JDK... It's really not much more confusing than what others use, and as to what you need to install for something.

.Net core apps should be a portable application (portable as in the runtime is compiled in)... Yeah, it is a little confusing, and hopefully removing some of the separate terminology will help. A lot of what has changed, is that you will likely be developing .Net Core (or Xamarin apps) that will target a given platform for running in... Most of the rest should be cross-platform modules that install via nuget (platform/language package manager) and bundled with the application output.

Re: Announcing .NET Core 1.0

#216

Earlier quoted context omitted.

You can go ahead with PostreSQL if you use Entity Framework and Code First approach. I used it many times and I was able to quickly jump from PostreSQL to MS SQL and back. It just works. With EF I don't see any reason why I should tie to any particular SQL database

Personally, I prefer writing SQL by hand. That way I know exactly what will happen in a query. A database really is an important component of a system and shouldn't be treated like a dumb data store where you just throw in any stuff you like through an ORM and hope it sticks there somehow.

False dichotomy, you can use both together and get the benefits of both an ORM and raw sql, each when they're the better choice.

Re: Announcing .NET Core 1.0

#217
post #191

Earlier quoted context omitted.

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.

What about Java SE?

Re: Announcing .NET Core 1.0

#218

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…

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 data that you shouldn't be allowed to see. If you detect "casual user" and "programmer" modes in your OS, the user shouts, "I don't want my computer knowing (and sharing) that much info about who I am!"

Even though most people aren't likely to ever need to use a fire extinguisher, you really want that interface to be simple and accessible. If you decide that because no one ever used this particular fire extinguisher, it doesn't need to be there, that's a decision that could make the difference between life and death. Moving a button on a form doesn't seem quite that serious, but it could still cause people to lose time or money, which adds up across all the people using the software.

Re: Announcing .NET Core 1.0

#219

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…

I'm not sure that the tooling will necessarily need to be updated as the rest seems to be nuget packages, that should be easy enough to update as you build an application.

I'm more of an outsider now, as I've been doing far more node/js dev lately than .Net ...

Re: Announcing .NET Core 1.0

#220

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.

The Story of the Ribbon video about Microsoft and data driven design. https://www.youtube.com/watch?v=Tl9kD693ie4

The Ribbon is, in my opinion, the use interface equivalent of a broken pull tab on a can of corn. I know it is there, I know that I'm supposed to use it, but I can't because it is broken.
Post reply on HN