Live data from Hacker News

C# is the past, the present and the future

blog.filipekberg.se

21–30 of 57 posts

Re: C# is the past, the present and the future

#21

He clearly works for MS and probably on the team that works on C#, which is why I find it odd that he touts Mono as a feature. If MS was serious about .NET everywhere, they'd sponsor Mono/Xamarin, or offer native .NET support for OSX and Linux instead of using the Mono community's hard work to toot their own horn. C# is a great language and has evolved beautifully, but many people will still continue to avoid it beca…

He isn't MSFT staff, read his "About the Author" page, he works for a Swedish company. Also he's a MS MVP, you can't be a Microsoft MVP and work for Microsoft at the same time.

Re: C# is the past, the present and the future

#23

I love C# as much as any MS fanboy would, but when people like Charles Petzold start abandoning C# and .NET for native C++ - http://blogs.msdn.com/b/msdnmagazine/archive/2013/01/08/1038... - to get more speed out of Windows 8 apps, then you have to start thinking maybe Microsoft is at least pushing C#/.NET out of the limelight - its not the be all and end all it used to be.

Second question down in that interview in response to petzold mentioning C++ :

Desmond: So should we be looking to move away from managed platforms and languages?

Petzold: No, no, no, not at all.

Re: C# is the past, the present and the future

#24

He clearly works for MS and probably on the team that works on C#, which is why I find it odd that he touts Mono as a feature. If MS was serious about .NET everywhere, they'd sponsor Mono/Xamarin, or offer native .NET support for OSX and Linux instead of using the Mono community's hard work to toot their own horn. C# is a great language and has evolved beautifully, but many people will still continue to avoid it beca…

He isn't MSFT staff, read his "About the Author" page, he works for a Swedish company. Also he's a MS MVP, you can't be a Microsoft MVP and work for Microsoft at the same time.

You're right. His use of "we" had me confused.

Re: C# is the past, the present and the future

#25

Earlier quoted context omitted.

I don't want to be a second class citizen. I don't want to be a second class citizen ever. I don't want to be a second class citizen. I don't want to be a second class citizen ever. "Really good" is so much different from "The Most Awesome Edition" you get with languages like Java or Ruby. I can tinker with a "Really good" tech on home projects all right (except I prefer Clojure), but not in the workplace.

Citizen. There is no alternative spelling. Sorry, you just used it so much!

Thanks for the correction because I always struggle with s/z in that position. It just makes so little sense! :(

Re: C# is the past, the present and the future

#26

He clearly works for MS and probably on the team that works on C#, which is why I find it odd that he touts Mono as a feature. If MS was serious about .NET everywhere, they'd sponsor Mono/Xamarin, or offer native .NET support for OSX and Linux instead of using the Mono community's hard work to toot their own horn. C# is a great language and has evolved beautifully, but many people will still continue to avoid it beca…

Nothing about that article suggested he works for MS and the style of writing alone is enough to convince me he doesn't.

Does Sun/Oracle sponsor all the different implementations of Java? Does the Python Foundation sponsor the various implementations of Python?

I'm guessing the work Microsoft are currently doing with Roslyn (compiler as a service) will benefit the various implementations also.

The C# spec is open and standardised, and if a particular group wants to pick it up and implement it, I find it a very weak argument to suggest that any company should throw money behind it.

Re: C# is the past, the present and the future

#27
post #7

Earlier quoted context omitted.

I'd suggest you give Mono and MonoDevelop ( http://monodevelop.com/ ) a try! It's really good and at least most of the web stuff that I've developed have just worked out of the box on Linux (Apache + Mono).

I don't want to be a second class citizen. I don't want to be a second class citizen ever. I don't want to be a second class citizen. I don't want to be a second class citizen ever. "Really good" is so much different from "The Most Awesome Edition" you get with languages like Java or Ruby. I can tinker with a "Really good" tech on home projects all right (except I prefer Clojure), but not in the workplace.

There are real companies out there making real money off Mono. So it's not a toy reserved for weekend tinkering. Enough companies trust Mono to use it in production.

Re: C# is the past, the present and the future

#28

He clearly works for MS and probably on the team that works on C#, which is why I find it odd that he touts Mono as a feature. If MS was serious about .NET everywhere, they'd sponsor Mono/Xamarin, or offer native .NET support for OSX and Linux instead of using the Mono community's hard work to toot their own horn. C# is a great language and has evolved beautifully, but many people will still continue to avoid it beca…

Nothing about that article suggested he works for MS and the style of writing alone is enough to convince me he doesn't. Does Sun/Oracle sponsor all the different implementations of Java? Does the Python Foundation sponsor the various implementations of Python? I'm guessing the work Microsoft are currently doing with Roslyn (compiler as a service) will benefit the various implementations also. The C# spec is open and…

But Java and Python are cross platform out of the box.

Re: C# is the past, the present and the future

#29

I would like to try it out but I'm not on Windows obviously, and I won't work to become a second class citizen ("What do you use? Mono? That's not supported"). Also, most of tooling seems to be proprietary, Windows-only too. So I'd stick to JVM.

I'm sharing your opinion. JVM is an excellent choice, whether doing Java or other JVM-based language.

Re: C# is the past, the present and the future

#30

Earlier quoted context omitted.

I don't want to be a second class citizen. I don't want to be a second class citizen ever. I don't want to be a second class citizen. I don't want to be a second class citizen ever. "Really good" is so much different from "The Most Awesome Edition" you get with languages like Java or Ruby. I can tinker with a "Really good" tech on home projects all right (except I prefer Clojure), but not in the workplace.

There are real companies out there making real money off Mono. So it's not a toy reserved for weekend tinkering. Enough companies trust Mono to use it in production.

I'm happy for them, but I'm not going to risk it. The reward is nice but not nearly worth the risk.

When adopting Java, you can trust it will just work, but with Mono you have to bet it's going to work, you're not going to run into compatibility problems and tooling will be adequate.

Post reply on HN