5 ms·
Yep, and check out System.Console for some horrors in the mono runtime.
by bigdubs 12y ago
Yep, and check out System.Console for some horrors in the mono runtime.
- rikkus 12y agoSystem.Console isn't something that most apps rely on. It's handy for printing something out in a tiny one-file test app, but generally not relied upon for bigger apps.
- JetSpiegel 12y agoAre you saying core .NET libraries are worthless? Because in that case what's the point? Why not just use Java.
- eropple 12y agoI'm sorry, but I have literally no idea how this post follows from the one you replied to?
- BinaryIdiot 12y ago> I'm sorry, but I have literally no idea how this post follows from the one you replied to? Literally? Well it is visually displayed under it and to the right :P
- BinaryIdiot 12y agoDamn, I liked my joke...
- bigdubs 12y agoAre servers / daemons not a common usecase? Most, if not all, of the apps I write on a daily basis do not have GUI.
- rikkus 12y agoIs this on a UNIX? If so, yes, it's common to write to stdout/stderr there. Not in Windows, though - anything which is long-running tends to be a Windows Service and there's no point writing to System.Console from there because no-one will see it! I haven't done much .NET on UNIX but if I was doing so, I'd probably want something a bit more UNIX-friendly than System.Console, though I know it does have the ability to deal with different streams.
- katbyte 12y agoLinks to some examples?