4 ms·

To be fair, C# is a chore without good tooling. I used to use omnisharp with atom and frankly it was just rubbish. It crashed all the time and required constan

To be fair, C# is a chore without good tooling. I used to use omnisharp with atom and frankly it was just rubbish. It crashed all the time and required constant restarts, and (still) takes a massive amount of time (and memory) to start. I went back to using golang, and didn’t regret it for a second. The tooling in go is excellent and you can use a simple editor for many things. That’s really compelling for people. So... to be fair, if you were to idly pickup .net core as a linux user, and expect vim or emacs to do the job, you’ll find it a terrible experience. ...but, with the right tooling, it can be really great. vs, cscode or rider (not free) make using c# a pleasure to work with. The dotnet cli tool is still quite terrible (how do you install dotnet watch again? why does it take 25s to restart a simple web app? You think git has obscure inconsistent incomprehensible command line flags...? ha! remind me why ‘dotnet build’ is running like 50 shell commands from the .csproj file...but only in this configuration you didn’t specify excplictly? surprise!) ...but its usable, and its slowly improving. I feel like a lot of C# enthusiasts shoot down complaints as people being rubbish, or trolling or ‘doing it wrong’; but the reality is c# on a platform other than windows is new, and still pretty raw. Pointing people in the right direction (you do need a proper IDE) and acknowledging that doesn’t suit everyone is better than telling them they’re ‘doing it wrong’; thats just jerk behaviour and comes off as fanboiism.

jackmott 9y ago
Can you explain why you need a good ide for C# as compared to other languages?
paulddraper 9y ago
C#'s bread-and-butter was desktop apps and then web servers. I've yet to see good Windows GUI support for Go.
pjmlp 9y ago
Let me know when Go has something comparable to Windows Forms, WPF, UWP, Xamarin.Forms, Avalonia. Oh, and when I have to use Go, I find a chore to write generic code as if I was back in 1992 using Borland C++ 2.0 for MS-DOS, with pre-processor based code generation for BIDS or still using Java 1.4 (EOL in 2008).
- Suman123 9y ago
  We provide very beautiful escorts services in India, Our all escorts girl give you 100% satisfaction your demand. If you want to know more information please go to our website. www.sumansaxena.in Mob-+91-9205915046
- shadowmint 9y ago
  When was the last time you wrote a micro service that compiled to a single binary and interop'd seamlessly using grpc in C#? I'm going to guess the answer is never, because it's basically impossible to do. Do you care? I doubt it, but some people really do. It's just different use cases for different things. Sure, go has its problems, but needing a large heavy IDE isn't one of them. That's really important to some people. /shrug > Oh, and when I have to use Go, I find a chore to write generic code... Oh man, don't even start. If you don't like go, don't use it. It was just one example of tooling that's better than C#. Rust, node, clojure, heck, even python has a better story for 'pick up and start using' than C# does at the moment. Do we really need to start digging down into how fundamentally terrible nuget is as a package manager, and how I personally find it like installing Master of Magic using 3 1/4 inch disks one by one when it screws up, or the feed screws up (like it did TODAY for about 4 hours)? nah. No one cares. Let's just leave it at: There are some valid concerns people have with the C# ecosystem, and using C# on non-windows platforms. It's a work in progress. At least we now have a coherent direction for everything going forward~
  - pjmlp 9y ago
    > I'm going to guess the answer is never, because it's basically impossible to do. You mean by using something like Mono -aot, CoreRT, IL2CPP? > Do we really need to start digging down into how fundamentally terrible nuget is as a package manager, No, because in spite its issues, it still runs circles around the half-baked solutions that Go devs are still trying to fix.
    - shadowmint 9y ago
      I'm not even going to bother. Nuget is such a pile of rubbish it's not even worth arguing about; if that's the best package manager you've ever used, you should really go check https://github.com/fsprojects/Paket https://github.com/fsprojects/Paket out. (they also helpfully articulate why nuget isn't really very good) The irony is that the folk from go-world have finally acknowledged the package management solution they have is really terrible, and they're building a lovely new one (https://github.com/golang/dep https://github.com/golang/dep). Maybe sometime in the future you'll be eating your words, when go has a lovely package manager. ...and c# still has nuget. :)

jackmott 9y ago

Can you explain why you need a good ide for C# as compared to other languages?

paulddraper 9y ago

C#'s bread-and-butter was desktop apps and then web servers. I've yet to see good Windows GUI support for Go.

pjmlp 9y ago

Let me know when Go has something comparable to Windows Forms, WPF, UWP, Xamarin.Forms, Avalonia. Oh, and when I have to use Go, I find a chore to write generic code as if I was back in 1992 using Borland C++ 2.0 for MS-DOS, with pre-processor based code generation for BIDS or still using Java 1.4 (EOL in 2008).

Suman123 9y ago
We provide very beautiful escorts services in India, Our all escorts girl give you 100% satisfaction your demand. If you want to know more information please go to our website. www.sumansaxena.in Mob-+91-9205915046
shadowmint 9y ago
When was the last time you wrote a micro service that compiled to a single binary and interop'd seamlessly using grpc in C#? I'm going to guess the answer is never, because it's basically impossible to do. Do you care? I doubt it, but some people really do. It's just different use cases for different things. Sure, go has its problems, but needing a large heavy IDE isn't one of them. That's really important to some people. /shrug > Oh, and when I have to use Go, I find a chore to write generic code... Oh man, don't even start. If you don't like go, don't use it. It was just one example of tooling that's better than C#. Rust, node, clojure, heck, even python has a better story for 'pick up and start using' than C# does at the moment. Do we really need to start digging down into how fundamentally terrible nuget is as a package manager, and how I personally find it like installing Master of Magic using 3 1/4 inch disks one by one when it screws up, or the feed screws up (like it did TODAY for about 4 hours)? nah. No one cares. Let's just leave it at: There are some valid concerns people have with the C# ecosystem, and using C# on non-windows platforms. It's a work in progress. At least we now have a coherent direction for everything going forward~
- pjmlp 9y ago
  > I'm going to guess the answer is never, because it's basically impossible to do. You mean by using something like Mono -aot, CoreRT, IL2CPP? > Do we really need to start digging down into how fundamentally terrible nuget is as a package manager, No, because in spite its issues, it still runs circles around the half-baked solutions that Go devs are still trying to fix.
  - shadowmint 9y ago
    I'm not even going to bother. Nuget is such a pile of rubbish it's not even worth arguing about; if that's the best package manager you've ever used, you should really go check https://github.com/fsprojects/Paket https://github.com/fsprojects/Paket out. (they also helpfully articulate why nuget isn't really very good) The irony is that the folk from go-world have finally acknowledged the package management solution they have is really terrible, and they're building a lovely new one (https://github.com/golang/dep https://github.com/golang/dep). Maybe sometime in the future you'll be eating your words, when go has a lovely package manager. ...and c# still has nuget. :)