C# is the past, the present and the future

Re:C# is the past, the present and the future by guard-of-terra on Friday January 11, 2013 @06:09AM (#5042212)

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.

[ Parent | on HN ]

Re:C# is the past, the present and the future by mattmanser on Friday January 11, 2013 @06:31AM (#5042249)

Citizen.

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

[ Parent | on HN ]

Re:C# is the past, the present and the future by guard-of-terra on Friday January 11, 2013 @06:56AM (#5042312)

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

[ Parent | on HN ]

Re:C# is the past, the present and the future by jinushaun on Friday January 11, 2013 @07:02AM (#5042328)

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.

[ Parent | on HN ]

Re:C# is the past, the present and the future by guard-of-terra on Friday January 11, 2013 @07:27AM (#5042374)

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.

[ Parent | on HN ]

Re:C# is the past, the present and the future by jackalope on Friday January 11, 2013 @07:48AM (#5042419)

Java comes with its own problems, especially in enterprise environments where you might be pinned to a single version. There are plenty of insecure JVMs out there that can't be upgraded on both servers and clients, mainly to ensure compatibility or meet support requirements.

[ Parent | on HN ]

Re:C# is the past, the present and the future by guard-of-terra on Friday January 11, 2013 @07:50AM (#5042424)

I don't see how it is relevant WRT considering a language/platform for a new project. You're talking about legacy stuff. I don't see how this can't happen to project in any language (PHP? Ruby? Perl? C#?)

[ Parent | on HN ]

Re:C# is the past, the present and the future by z92 on Friday January 11, 2013 @07:39AM (#5042396)

That's news to me. Not that I disbelieve. Really interested. Can you point me to some use cases? Why do they not just use Windows?

[ Parent | on HN ]

Re:C# is the past, the present and the future by gebe on Friday January 11, 2013 @08:28AM (#5042551)

Mostly on mobile I would guess. Xamarin has a showcase on their site: http://xamarin.com/apps .

Also every game made in Unity is using Mono, which is _a lot_ of games. The Playstation Vita and Wii U uses Mono as well for third party development.

[ Parent | on HN ]