5 ms·
>"Under-30 dev here. Been programming in C# for the past 3.5 years now, and loving every minute of it." Mid 30's here. I work mostly on C++ but I have to jump
by pmelendez 12y ago
>"Under-30 dev here. Been programming in C# for the past 3.5 years now, and loving every minute of it."
Mid 30's here. I work mostly on C++ but I have to jump into C# code once in a while. I agree that C# is a very productive language and I love how it never gets in your way ("Do you say you don't want to use a common interface for your generics? Use dynamic!").
My only "complaint" is that C# is so indulgent that it gets boring at times, which might actually be a feature.
- to3m 12y agoC# is oft underrated, in my view. It's very quick to code in, is part of a large (if Windows-centric) ecosystem, and has been generally fairly tastefully designed. Compared to other languages you might compare it to, its designers aren't afraid to be a bit avant garde at times (unlike Java), it's got static typing (unlike Python), it's got garbage collection (unlike C), and... well, I know Go programmers hate it when people drop the G-bomb. But it's got that too. Unlike Go.
- pmelendez 12y agoG-bomb?
- andrewchoi 12y agoI assume he means generics.
- to3m 12y agoMaybe... :) I was a little circumspect because the usual response to any suggestion that a lack of generics might be some kind of problem is - generally - not positive. But my point is merely that C# has this thing, and Go doesn't. If I knew enough about Go to say instead that it lacks something else that C# has, I'd have done that...