Hacker News new | ask | show | jobs
by MangoCoffee 604 days ago
I use Visual Studio from work and personally subscribe to JetBrains.

For those developing commercial software on a budget, Visual Studio Code is an excellent option.

Although it lacks some features of JetBrains and Microsoft tools, pairing the .NET CLI with VS Code can still deliver impressive results.

if you can afford $10 monthly, integrating GitHub Copilot with VS Code can elevate it to a fancy, lightweight IDE

1 comments

That's my exact workflow nowadays. The best text editing experience with GH copilot and lowest battery footprint makes using a VSC a no-brainer. It's especially nice since it also happens to be the choice for Rust, so I experience very little friction, not having to switch an editor and using capable CLI of .NET and Cargo.

For advanced scenarios Rider still rules, and this change is a very welcome one. I hope it will help with promoting .NET as the first choice where teams historically picked Go (which is worse).

    >  I hope it will help with promoting .NET as the first choice where teams historically picked Go (which is worse)
Curious in what ways specifically you think Go is worse than .NET and what contexts?
With discipline, it is both more expressive by having a better and more powerful type system, and faster by allowing much finer control over code execution, data layout and allocations as well as offering actual GC tuning options. .NET's compiler is much more capable too, and the rate of improvement is not slowing down. It also has much richer package for writing line-of-business applications productively. The main advantage of Go used to be and still is "culture". But once you apply such minimalism mentality to C#, it gives a much better end result.
Why battery footprint would be even relevant for day2day?

Do you develop outside?