3 ms·

> Gave it a serious go but it still lives inside the Windows + Visual Studio bubble. I work in a small shop and most of the developers use Visual Studio with L

> Gave it a serious go but it still lives inside the Windows + Visual Studio bubble. I work in a small shop and most of the developers use Visual Studio with Linux or a Mac. Most of the developers that don't bother with anything outside of Windows won't be open sourcing their libs or documenting their stuff anyways. This may have been true back in 2016/7 when .NET Core first turned up but it just isn't true anymore. > Trying to use .NET on Linux with Visual Studio Code is pain: .NET developers expect you to learn APIs through intellisense and don't publish API docs, I've used VS Code for small projects fine on my Mac. However I can see it being a pain on larger projects and you will need a large IDE. However the same could be said for a large Java project. > Windows tutorials assume you're running Visual Studio, and a lot of MS's own API docs are bewildering with .NET jargon that you won't understand. I don't want to sound like a dick, but yes the Windows tutorials will expect you to use Visual Studio as that is the IDE that primary IDE of people using Windows. As for complaints about jargon. As a C# developer that now transitioning to Python. The Python docs having lot of Python Jargon you won't understand (at first). Every language has its own jargon.

VadimPR 5y ago
Java projects publish Javadoc which is good - you can sit down and understand an API. It's not the same story on .NET. > Windows tutorials will expect you to use Visual Studio as that is the IDE that primary IDE of people using Windows. Yep, hence the bubble. Python doesn't have this problem, for example.
- net_greybeard 5y ago
  > Java projects publish Javadoc which is good - you can sit down and understand an API. It's not the same story on .NET. Almost all the projects I use with .NET have sufficient docs on their sites. MSDN has the full docs on their site. If there are specific projects that are a problem that are outside of that. Well that is a problem with their project, go and complain to them. > Yep, hence the bubble. Python doesn't have this problem, for example. Yes Python does have similar problems. A lot of time people assume you are using a *nix machine and if you aren't then you normally have to faff with some work around. Go has the same problem a lot of things just don't work properly on Windows (at the least the last time I bothered). The same is true with Java, Go, Ruby etc. As for the tutorials. I've just gone on the ASP.NET site and there is a tutorial for Windows, Linux and MacOS in the tabs on the site.

VadimPR 5y ago

Java projects publish Javadoc which is good - you can sit down and understand an API. It's not the same story on .NET. > Windows tutorials will expect you to use Visual Studio as that is the IDE that primary IDE of people using Windows. Yep, hence the bubble. Python doesn't have this problem, for example.

net_greybeard 5y ago
> Java projects publish Javadoc which is good - you can sit down and understand an API. It's not the same story on .NET. Almost all the projects I use with .NET have sufficient docs on their sites. MSDN has the full docs on their site. If there are specific projects that are a problem that are outside of that. Well that is a problem with their project, go and complain to them. > Yep, hence the bubble. Python doesn't have this problem, for example. Yes Python does have similar problems. A lot of time people assume you are using a *nix machine and if you aren't then you normally have to faff with some work around. Go has the same problem a lot of things just don't work properly on Windows (at the least the last time I bothered). The same is true with Java, Go, Ruby etc. As for the tutorials. I've just gone on the ASP.NET site and there is a tutorial for Windows, Linux and MacOS in the tabs on the site.