Anyone who thinks C# is a bad language has never used LINQ to write a data mining app in an afternoon.


Good fucking luck touching that kind of productivity in C++.

Depends on a lot of factors. If I were making a game for Linux, I wouldn't bother with C# too much.

Your loss.


http://www.monogame.net/

No, my gain .

I didn't know that such a thing existed.

Their showcase games are quite impressive. Bastion, Draw a Stickman, Skulls of the Shogun, Fez. I just wish they would implement the XNA toolchain so we could convert the assets into the correct formats without VS 2010.

I like to "play" with the stuff I code. Aka "lets try this number instead of that one!" "Lest try more iterations!" And so on.

I like to "play" with the stuff I code. Aka "lets try this number instead of that one!" "Lest try more iterations!" And so on.

You'd make an awesome tester . You'll break stuff left and right .

One thing I still find odd is seeing people still compare C# to C++ and vice versa, the reason this is so unusual (for me at least) is that both languages work excellent together but often comparison threads / posts are made to encourage the use of one over the other.

Using C# / C++ together reminds me of those hybrid cars that run on electric for short distances but on petrol long, or something like that.

Pros of C#++

Using the best of both languages

Spending more time working and less time comparing or feeling insecure about chosen language

Learning and improving in 2 languages

Able to work with a lot more libraries that don't necessarily have wrappers or updated ones

Cons of C#++

Compile times can suffer at times naturally because of C++

No more invites to C# / C++ dinner parties :(

Love: Implementing that algorithm and it works, the first time. Those are nice rare moments. I guess I just generally like the feeling that I've been productive, too.

Hate: Those times when I'm awake but (very) aware that my mind has just stopped problem solving until I sleep, and can't do anything about it (besides sleep). No amount of caffeine or exercise etc. fixes this.

One thing I still find odd is seeing people still compare C# to C++ and vice versa, the reason this is so unusual (for me at least) is that both languages work excellent together but often comparison threads / posts are made to encourage the use of one over the other.

Using C# / C++ together reminds me of those hybrid cars that run on electric for short distances but on petrol long, or something like that.

Pros of C#++

Using the best of both languages

Spending more time working and less time comparing or feeling insecure about chosen language

Learning and improving in 2 languages

Able to work with a lot more libraries that don't necessarily have wrappers or updated ones

Cons of C#++

Compile times can suffer at times naturally because of C++

No more invites to C# / C++ dinner parties

but, sadly, this crosses over into areas where implementation differences show up (at least, in my experience, if portability matters):

for example, .NET has C++/CLI, Mono doesn't;

.NET interfaces fairly directly with native code (easily allows calls between native and CLR code, passing data structures back and forth, ...), whereas Mono gives more limited P/Invoke functionality (call out), and otherwise requires the use of an explicit API (which is specific to Mono), ...

this would mean that implementation portability would require wrapping it (or writing a "glue generator" tool), and adding a lot of hassle.

also, Mono is a bit of a beast code-wise, and is difficult to get built on Windows (hindering a plain Mono route), ...

so, yeah, it is mostly a matter of implementations...

granted, yes, it works a lot better if portability isn't as much of a concern.

I had once looked at DotNetAnywhere, but ended up not using it.

more fun is if you want to be able to eval C# code or load it from source.

the path of least resistance in my case was mostly just to continue on in the same direction (using a mix of C and my own scripting language).

Ah yes, I often forget about Linux / Apple. Sadly both OS didn't appeal to me during my modest time playing with them because of major reasons and concerns, so for now I am happily pure MS / Windows :) and I am yet to have any complaints

The thing I love the most on programming is, like cited before, findind a solution to a bug after a sudden realization.

The thing I hate the most is useless/misleading error information.

I love prototyping games, and getting the basic builds up.

I hate polishing off the ui stuff, and making all the buttons. I'm perfectly fine with making things work by pressing a key, and using simple text to represent the state of things(such as health/mana/stamina). But alas not everyone enjoys that...simplicity, it's just boring to position an ui label, write the code to make it say something, position button, write the code to make it do stuff, etc. then you've gatta make sure they all look nice, and flow right. it's just so boring.

I'm working on a text-mode game for just that reason, with the basic idea of "Let me just tell you what is happening and you can respond when I let you." Going well.

I love getting the ball rolling, but I have to kick myself in the pants to keep working on it. That goes with everything I do which I don't get paid for, of course.

When people make a post and don't specify a language (yes, even on this forum). It makes it more annoying to have to go in there and look through it before actually filtering for the things that you're actually good in and going only for those questions.