5 ms·

I work at a company where we have built one of our products (a large distributed system that tracks television content worldwide) completely on .NET. I love C#,

I work at a company where we have built one of our products (a large distributed system that tracks television content worldwide) completely on .NET. I love C#, it's a very decent blend between a whole lot of languages and additions of LINQ and async/await kept it relevant. Visual Studio is the best IDE I've worked with, not because it's such a good editor but because it has a sane debugger that is actually helpful. I still wouldn't run my startup on .NET though, for a number of reasons. Mono simply isn't there yet. Code that works fine on Windows mysteriously stops working on Mono due to threading or GC vagaries (yes, even in the latest version). This isn't a dealbreaker, but it is pretty annoying especially since debugging these kinds of problems are of precisely the kind that I don't want to debug. The ecosystem is really quite poor compared to, say, JVM or Node. For all the faults of either, there is a LOT of stuff going on and there is a LOT of innovation that is sorely lacking from the .NET world. .NET usually catches up eventually but it's either late or half-hearted (just look at the progress of NHibernate vs. Hibernate). I think ASP.NET vNext is a step in a very good direction and I hope to be able to change my opinion sometime next year.

darylteo 12y ago
> NHibernate vs. Hibernate As a counter argument to that (specifically), we don't really need NHibernate when we have Entity Framework.
- royjacobs 12y ago
  When you start from scratch I'd agree with you, but if you want to interface with a legacy database and you need some more esoteric mappings and user-defined types then I'm not sure how happy you'd be with EF.
- steviee 12y ago
  As a counter-counter point: You absolutely need NHibernate (or something else) when you use EF. Steviee
  - beauzero 12y ago
    The proof is in Orchard CMS.
xtracto 12y ago
> Mono simply isn't there yet. Code that works fine on Windows mysteriously stops working on Mono due to threading or GC vagaries (yes, even in the latest version). I remember having to maintain a small C# SDK in my previous work. That was a bit of a headache given that we were a 100% OSX shop. I installed MonoDevelop and libraries in my Mac to try to make some changes there, just to find out that Mono has not implemented some .NET standard encryption libraries. I really appreciate what Miguel and team has achieved with Mono, but it is still incomplete, so from my experience it is not really an option. We ended installing XP in a virtual machine to modify the code.
- knocte 12y ago
  > Mono has not implemented some .NET standard encryption libraries. Good find! Did you file a bug report?
knocte 12y ago
> This isn't a dealbreaker, but it is pretty annoying especially since debugging these kinds of problems are of precisely the kind that I don't want to debug. It's understandable that you don't want to (or don't have time to) debug them. But filing bug reports in Mono's bugzilla is appreciated, at least (maybe the Mono team can debug the problems for you).
deleted 12y ago
[deleted]

darylteo 12y ago

> NHibernate vs. Hibernate As a counter argument to that (specifically), we don't really need NHibernate when we have Entity Framework.

royjacobs 12y ago
When you start from scratch I'd agree with you, but if you want to interface with a legacy database and you need some more esoteric mappings and user-defined types then I'm not sure how happy you'd be with EF.
steviee 12y ago
As a counter-counter point: You absolutely need NHibernate (or something else) when you use EF. Steviee
- beauzero 12y ago
  The proof is in Orchard CMS.

xtracto 12y ago

> Mono simply isn't there yet. Code that works fine on Windows mysteriously stops working on Mono due to threading or GC vagaries (yes, even in the latest version). I remember having to maintain a small C# SDK in my previous work. That was a bit of a headache given that we were a 100% OSX shop. I installed MonoDevelop and libraries in my Mac to try to make some changes there, just to find out that Mono has not implemented some .NET standard encryption libraries. I really appreciate what Miguel and team has achieved with Mono, but it is still incomplete, so from my experience it is not really an option. We ended installing XP in a virtual machine to modify the code.

knocte 12y ago
> Mono has not implemented some .NET standard encryption libraries. Good find! Did you file a bug report?

knocte 12y ago

> This isn't a dealbreaker, but it is pretty annoying especially since debugging these kinds of problems are of precisely the kind that I don't want to debug. It's understandable that you don't want to (or don't have time to) debug them. But filing bug reports in Mono's bugzilla is appreciated, at least (maybe the Mono team can debug the problems for you).

deleted 12y ago

[deleted]