20
How is Visual Studio?
(kbin.social)
This magazine is dedicated to discussions on programming languages, software development, and coding. Whether you are a beginner programmer or an experienced developer, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as coding languages, software engineering, web development, and more. From the latest trends and frameworks to tips and tricks for debugging, this category covers a wide range of topics related to programming.
I started using Visual Studio (not Code, wtf were they thinking when they named these things) around 15 years ago.
Back then, it helped me a lot learning C# through excellent (= mostly very fast) code completion/suggestion and lookup tools (peek definitions etc).
I still use it (mostly for Unity), but maybe there are now better IDEs of which I am not aware of.
Currently, I still love the code completion and lookup features, but it became pretty overloaded with features and takes very long to load on my old laptop. Once up and running, it's fine.
What's funny is that originally "visual" was the selling point in that you design your programs visually rather than through code. With the naming of VS code, they've gone full circle. It's a video game adaptation of a movie adaptation of a video game.