News for hackers. Stuff that matters.
Re:Announcing .NET Core 1.1 by arenaninja on Wednesday November 16, 2016 @01:01PM (#12969564)
Lots of news coming out of Microsoft's Connect event. C# is a great language, .NET Core makes it available cross-platform, and now the tooling is being announced (whether it's on par with what's available on Windows is TBD)
Re:Announcing .NET Core 1.1 by hnrodey on Wednesday November 16, 2016 @05:00PM (#12971976)
IMO The ecosystem of tools on Windows for C#/.NET is what makes it special stack. Resharper and LinqPad are two notable tools that I consider vital to my everyday workflow that just simply don't exist for macOS.

At home I use macOS primarily and I'm trying to ramp up on .NET Core for a few personal projects and I'm having a tough time trying to find a suitable dev environment that provides me with the same speed/comfort that I get on a Windows machine and so far it's tough. Project Rider on macOS is coming along nicely but that still leaves no LINQPad which is super handy for working on small bits of code with near instant results. The feedback loop is so short when using Linqpad it's insane.

Re:Announcing .NET Core 1.1 by mattmanser on Wednesday November 16, 2016 @07:48PM (#12973159)
You haven't needed linqpad since vs 2015, which has a C# repl in it.

I also don't get the point of resharper. Apart from being slow as molasses, it's ridiculously over opinionated to the point where is makes existing code a mess of squiggles. And it's intellisense is super dumb as it redlines while you're still typing, which is very distracting.

The only great part of it, the quick find, is now in vs 2015. Ctrl-,. I think it literally just came in with the last patch.

Re:Announcing .NET Core 1.1 by hnrodey on Wednesday November 16, 2016 @09:10PM (#12973610)
I wasn't aware of the enhancement in VS2015. I'll definitely look at that functionality.

VS2015 has made up a lot of ground for what R# lacked but the static analysis still isn't there. You have to learn what errors/notes mean and how to interpret the results because they are very meaningful. Point blank - writing code with Resharper will lead to higher quality code.

And yeah, some part of my Resharper love is just an old habit. I've been using R# since VS2005 when the IDE lacked a lot of critical features that R# plugged. Now a lot of it is just habits and keyboard shortcuts and it's only a few hundred dollars for a license which still pays for itself throughout the course of the year.

Re:Announcing .NET Core 1.1 by mattmanser on Thursday November 17, 2016 @11:12AM (#12978675)
I simply disagree about higher quality code. One of my junior colleagues once did a "let's apply a bunch of resharper recommendations". It was not pretty. Its suggestions are almost always pedantic and puerile that don't improve code quality in any meaningful way, at least in the out-of-the-box config.

It's nice when it picks up some stupidity like an always false condition, but the out-of-the-box instance has so many stupid rules that after turning more and more off it off, I gave up on it.

And this isn't the first time I've given it a go.

Re:Announcing .NET Core 1.1 by jombiezebus on Wednesday November 16, 2016 @07:51PM (#12973179)
For working on small bits of code with quick results, https://dotnetfiddle.net/ is a great online solution.