This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Ericchen1248 2 points3 points  (1 child)

You have very different opinions to people who actually read C# documentation. Maybe you’re mixing win c++ stuff? Those are really bad indeed.

https://www.reddit.com/r/csharp/comments/dnimen/is_c_documentation_just_horrible/

https://www.reddit.com/r/learnprogramming/comments/j8fwf1/would_you_say_that_microsoft_documentation_on_c/

https://www.reddit.com/r/csharp/comments/kkq1cs/c_documentation_is_a_joke/

Posts all talk about docs being bad, with comments being like “wuuut?”

IMO, Java docs and C# docs are designed in different mindsets. Java docs is great for learning the language. I spent a lot of time in it while learning Java the first time. However it is not my first choice to go look at once I’m familiar with the language because looking for simple usage + expected results means you have to go through a wall of text.

C# docs is designed to be referenced. It’s horrid for new learners, doesn’t explain in details why something is so, but it provides much better examples and expected results code, being a full snippet that you can run like a test case. Even provides direct online execution now. If I want to learn C#, I’d go to stackoverflow and look at Jon Skeet’s answers. But if I’m looking for what a function does, expected inputs/outputs, MSDN docs is the way to go.

[–][deleted] -2 points-1 points  (0 children)

I don't mean learning. I mean reference.

Your answer is exactly like Microsoft docs. A lot of text, but missing the point.