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.
I've yet to see good Windows GUI support for Go.
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).
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~
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.
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 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).
Maybe sometime in the future you'll be eating your words, when go has a lovely package manager.
...and c# still has nuget.
:)
If you’re trying to write C# in emacs you’re doing it wrong. C# has probably the best tooling in the world if you embrace it.
I love c#, but I've been using it since '05. I don't envy newcomers.
I am the current maintainer of omnisharp-emacs and would love to know out what are the most pressing problems people encounter using C# on emacs via omnisharp - https://github.com/OmniSharp/omnisharp-emacs
How does time travel debugging work in emacs?
So you are expected to download VS Code, use sdb or something else if you want to have step-by-step debugger...
Would you be willing to submit an issue to github about the problems you have encountered (if not already?)
I would love to make the experience of using C# on emacs with omnisharp-emacs easier for people.
There's the languages (C#, F#), there's the runtime (CLR - Common Language Runtime), and then various frameworks (including the base framework, and the ASP.NET framework). Then there's the difference between the original variants of these and the new 'Core' variants.
Plus there's various other related bits like the .NET Standard projects which are meant for library developers to target to make library cross-platform portability easier.
As for difficulty getting intellisense working via emacs - that's certainly been something demoed, but it's not really a well tested use-case at this time.
If you're coming at it from a non traditional (Windows) developer perspective - then you're looking at a massive ecosystem in flux and in migration from being a primarily single platform to multiplatform.
docs.microsoft.com is steadily improving this.
> I've tried no less than 10 times over the last few months to get "intellisense" working in emacs via roslyn and it has never worked.
https://github.com/OmniSharp/omnisharp-emacs
Are you not using this? Works great for me.
If you want getting started to be less of a chore use VS Code, VS, Rider, VS for Mac, Xamarin Studio, or Monodevelop.
I’m hoping that things will slow down and converge again in a while.
CoreFX? CoreCLR? No idea what these are or what they're for.
And don't get me started on the dumpster fire that is roslyn. I've tried no less than 10 times over the last few months to get "intellisense" working in emacs via roslyn and it has never worked.
C#'s a cool language that I want to like but it's just so much work to get started with.