3 ms·
You see the problem? Not really. If you don't like windows, use Linux or OS X and Mono.
by __--__ 13y ago
You see the problem?
Not really. If you don't like windows, use Linux or OS X and Mono.
- makomk 13y agoMono works just well enough to convince people that C#/.NET is an acceptable cross platform solution. By the time they realise it's so buggy and unreliable compared to .NET that they'll have to shell out for Windows licenses, they're stuck with it. See, for instance, keithwarren's comments in this discussion: he hypes up Mono-based cross-platform support in what's currently the top comment on this submission[1], but when someone who's actually tried Mono replies and talks about the problems they've had with it, he makes it clear that they should shut up, forget about Mono and use Windows[2]. [1] https://news.ycombinator.com/item?id=6659798 https://news.ycombinator.com/item?id=6659798 [2] https://news.ycombinator.com/item?id=6660976 https://news.ycombinator.com/item?id=6660976
- MichaelGG 13y agoThe first time I used Mono in a production environment (part of a payment connector running on a Linux system) was around a decade ago. Since then I've had daemons running 24/7 doing telecom processing (either routing decisions or call record management), written in F#, running on Mono. We build, debug, etc. on Windows, then deploy the binaries to Linux. It works surprisingly well. These aren't massive systems, and I tend to deplore the handful of core systems (i.e. website) on Windows but all the actual call handling goes on Windows. The real problem with Mono was the naive GC which for some applications had very degenerate and broken behaviour. AFAIK, the sgen GC has cleared that all up. Your characterization of the comments are very misleading.