Live data from Hacker News

Announcing September 2016 Updates for .NET Core 1.0

blogs.msdn.microsoft.com

11–20 of 31 posts

Re: Announcing September 2016 Updates for .NET Core 1.0

#11
post #2

It's great to see the HN community responding positively to news about .NET/Mono and related tech. I've been working with C#/.NET since 2008 and always felt it's a vastly superior platform to Java in every way. It's a shame it is taking so long for the wider tech community to realise this.

The two features I miss from java:

1. The compiler checks for exceptions being thrown and and makes you write a catch.

2. Anonymous inner classes.I prefer even handlers, but would still like this feature.

I think c# does a good job of always adding features that make it easier to write code.

Re: Announcing September 2016 Updates for .NET Core 1.0

#12
post #2

It's great to see the HN community responding positively to news about .NET/Mono and related tech. I've been working with C#/.NET since 2008 and always felt it's a vastly superior platform to Java in every way. It's a shame it is taking so long for the wider tech community to realise this.

I've spent the two halves of my career thus far working on each stack, and I really can't see where those sorts of claims come from, honestly. C# as a language is a win over Java, but from an operational perspective, it's a disaster--IIS is an absolute nightmare. Beyond that, I tend to think that because of the niceties that C# has over Java, that has somewhat held back .NET community adoption of some better practices (specifically immutability).

All that said, .NET Core is a huge win on the operational side of things, so it's definitely moving in the right direction.

Re: Announcing September 2016 Updates for .NET Core 1.0

#13
post #2

It's great to see the HN community responding positively to news about .NET/Mono and related tech. I've been working with C#/.NET since 2008 and always felt it's a vastly superior platform to Java in every way. It's a shame it is taking so long for the wider tech community to realise this.

I've spent the two halves of my career thus far working on each stack, and I really can't see where those sorts of claims come from, honestly. C# as a language is a win over Java, but from an operational perspective, it's a disaster--IIS is an absolute nightmare. Beyond that, I tend to think that because of the niceties that C# has over Java, that has somewhat held back .NET community adoption of some better practice…

See from Java perspective, it's just 20 years too late.

Re: Announcing September 2016 Updates for .NET Core 1.0

#14
post #2

It's great to see the HN community responding positively to news about .NET/Mono and related tech. I've been working with C#/.NET since 2008 and always felt it's a vastly superior platform to Java in every way. It's a shame it is taking so long for the wider tech community to realise this.

I've spent the two halves of my career thus far working on each stack, and I really can't see where those sorts of claims come from, honestly. C# as a language is a win over Java, but from an operational perspective, it's a disaster--IIS is an absolute nightmare. Beyond that, I tend to think that because of the niceties that C# has over Java, that has somewhat held back .NET community adoption of some better practice…

.Net isn't IIS. It's just one web server that can host it. And I'd take IIS over WebSphere any day!

Re: Announcing September 2016 Updates for .NET Core 1.0

#15
post #2

It's great to see the HN community responding positively to news about .NET/Mono and related tech. I've been working with C#/.NET since 2008 and always felt it's a vastly superior platform to Java in every way. It's a shame it is taking so long for the wider tech community to realise this.

I've spent the two halves of my career thus far working on each stack, and I really can't see where those sorts of claims come from, honestly. C# as a language is a win over Java, but from an operational perspective, it's a disaster--IIS is an absolute nightmare. Beyond that, I tend to think that because of the niceties that C# has over Java, that has somewhat held back .NET community adoption of some better practice…

I've also spent two halves of my career on each and I recently had to do a project that involved building a data pipeline on Azure. All of the C# pieces (HTTP endpoint, event consumer) were written in C# and deployed at Azure App Service/Cloud Services. I could have easily deployed the code in Docker containers running Linux, but the App/Cloud service deployment is very nice and abstracts the entire web server (Kestrel) away.

Anyway, I agree that operationally .NET has struggled, and of course the community was much different than other open source solutions, but it both have gotten much, much better in just the last few years.

Re: Announcing September 2016 Updates for .NET Core 1.0

#16

Earlier quoted context omitted.

I've spent the two halves of my career thus far working on each stack, and I really can't see where those sorts of claims come from, honestly. C# as a language is a win over Java, but from an operational perspective, it's a disaster--IIS is an absolute nightmare. Beyond that, I tend to think that because of the niceties that C# has over Java, that has somewhat held back .NET community adoption of some better practice…

See from Java perspective, it's just 20 years too late.

I see it as 10 years ahead.

Re: Announcing September 2016 Updates for .NET Core 1.0

#17

Earlier quoted context omitted.

I've spent the two halves of my career thus far working on each stack, and I really can't see where those sorts of claims come from, honestly. C# as a language is a win over Java, but from an operational perspective, it's a disaster--IIS is an absolute nightmare. Beyond that, I tend to think that because of the niceties that C# has over Java, that has somewhat held back .NET community adoption of some better practice…

.Net isn't IIS. It's just one web server that can host it. And I'd take IIS over WebSphere any day!

Me too.

Websphere is such a pain to use, yet it still is everywhere on enterprise projects.

Re: Announcing September 2016 Updates for .NET Core 1.0

#18
post #2

It's great to see the HN community responding positively to news about .NET/Mono and related tech. I've been working with C#/.NET since 2008 and always felt it's a vastly superior platform to Java in every way. It's a shame it is taking so long for the wider tech community to realise this.

I've spent the two halves of my career thus far working on each stack, and I really can't see where those sorts of claims come from, honestly. C# as a language is a win over Java, but from an operational perspective, it's a disaster--IIS is an absolute nightmare. Beyond that, I tend to think that because of the niceties that C# has over Java, that has somewhat held back .NET community adoption of some better practice…

IIS was really bad (has gotten better), but I don't see most Java EE stacks being much better.

At my last job we had two teams, one had a .NET stack, and the other had a Java EE stack, it was almost like someone had set up a lab to test which one was better (both were required to deliver very similar style LOB applications, one for one department and the other for another).

The .NET team consistently delivered a lot more value faster, and the Java deliverables always had reliability problems which they attributed to the JBoss setup. To be fair, the Java side was hampered by an "old-school" architect who refused to use the right tools for the job (even on the Java side, there are pretty decent frameworks and IDEs).

Re: Announcing September 2016 Updates for .NET Core 1.0

#19
post #2

It's great to see the HN community responding positively to news about .NET/Mono and related tech. I've been working with C#/.NET since 2008 and always felt it's a vastly superior platform to Java in every way. It's a shame it is taking so long for the wider tech community to realise this.

The two features I miss from java: 1. The compiler checks for exceptions being thrown and and makes you write a catch. 2. Anonymous inner classes.I prefer even handlers, but would still like this feature. I think c# does a good job of always adding features that make it easier to write code.

Interesting that you miss checked exceptions. Is one of the most criticized feature of the language, see Does Java need Checked Exceptions? [0]. Also in this discussion between Anders Hejlsberg and Bruce Eckel they are discussing why C# did not adopt them: The Trouble with Checked Exceptions [1]. Also Java theory and practice: The exceptions debate [2] discusses the more on the topic.

[0] http://www.mindview.net/Etc/Discussions/CheckedExceptions/

[1] http://www.artima.com/intv/handcuffs.html

[2] https://www.ibm.com/developerworks/library/j-jtp05254/

Re: Announcing September 2016 Updates for .NET Core 1.0

#20
post #2

It's great to see the HN community responding positively to news about .NET/Mono and related tech. I've been working with C#/.NET since 2008 and always felt it's a vastly superior platform to Java in every way. It's a shame it is taking so long for the wider tech community to realise this.

I've spent the two halves of my career thus far working on each stack, and I really can't see where those sorts of claims come from, honestly. C# as a language is a win over Java, but from an operational perspective, it's a disaster--IIS is an absolute nightmare. Beyond that, I tend to think that because of the niceties that C# has over Java, that has somewhat held back .NET community adoption of some better practice…

IIS != .NET
Post reply on HN