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 @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 ]