3 ms·

While it's tempting to air my perceived grievances I'm going to decide against it -- I've seen/done enough with C# that I know I will never choose it for a pers

While it's tempting to air my perceived grievances I'm going to decide against it -- I've seen/done enough with C# that I know I will never choose it for a personal project (or work on it for a professional project) ever again, not when options like Go, Haskell, NodeJS + Typescript, Rust, Lisps (clojure/clisp/racket/scheme) and even Java exist. I'm sure if I typed out some long list of things I think are sufficient about the language, someone will take it as an opportunity to "dispell myths" or show me how if I write ~20 lines of boilerplate, it'll be just like the language was ergonomic from the start. The C# community doesn't need another naysayer, but I did want to find out (maybe this is the wrong place to ask) from people who enjoy using it why they do.

Gibbon1 9y ago
My use case is I write a GUI tool in C#/.net, publish it and then hand it over to field service and production and they never bug me again unless they need a feature added. > and even Java exist. When you mention this, I think you are trolling. I can see starting a greenfield project in C#/.net. There isn't any reason to start a green field Java project. Just like there is little reason to start a greenfield C++ project.
- hardwaresofton 9y ago
  Ahh, that's an interesting use case, I haven't written many GUI tools and the last time I wrote one was in Java (Swing) and it wasn't terrible but wasn't great either, so C# is pretty good/ergonomic for it? When I say java, I mostly mean a JVM language... yeah I wouldn't really start a new project in Java, though I've heard nice things about JavaFX on the GUI side of things.
  - Gibbon1 9y ago
    Implementing GUI apps in C#/.net with visual studio basically just works. C# as a language is 'fine'. And generics seem to be well implemented. Microsoft documentation for simple stuff is reasonably clear. I think .net timers not so much.
GophersGoneWild 9y ago
Damn! Even JAVA? You mean business!
junke 9y ago
"clisp" is an implementation, Common Lisp is commonly abbreviated CL.

Gibbon1 9y ago

My use case is I write a GUI tool in C#/.net, publish it and then hand it over to field service and production and they never bug me again unless they need a feature added. > and even Java exist. When you mention this, I think you are trolling. I can see starting a greenfield project in C#/.net. There isn't any reason to start a green field Java project. Just like there is little reason to start a greenfield C++ project.

hardwaresofton 9y ago
Ahh, that's an interesting use case, I haven't written many GUI tools and the last time I wrote one was in Java (Swing) and it wasn't terrible but wasn't great either, so C# is pretty good/ergonomic for it? When I say java, I mostly mean a JVM language... yeah I wouldn't really start a new project in Java, though I've heard nice things about JavaFX on the GUI side of things.
- Gibbon1 9y ago
  Implementing GUI apps in C#/.net with visual studio basically just works. C# as a language is 'fine'. And generics seem to be well implemented. Microsoft documentation for simple stuff is reasonably clear. I think .net timers not so much.

GophersGoneWild 9y ago

Damn! Even JAVA? You mean business!

junke 9y ago

"clisp" is an implementation, Common Lisp is commonly abbreviated CL.