5 ms·

I have usually found, installed and started using a good javascript library in less time than it would take me to make sense of MSDNs enterprise-soup documentat

I have usually found, installed and started using a good javascript library in less time than it would take me to make sense of MSDNs enterprise-soup documentation.

manigandham 7y ago
What does MSDN have to do with this? Are you talking about C# and .NET specifically? Have you seen the current documentation? https://docs.microsoft.com/en-us/ https://docs.microsoft.com/en-us/
- lacampbell 7y ago
  Yes, I felt brave, so I went after everyones darling C#, and not an easy target like Java. I read C# documentation several times a week. I do not like it.
  - gmiller123456 7y ago
    Can you provide some examples of documentation you do like? While I can't ever remember reading some documentation and saying, "Wow, that was fun!", so I can't say there's any documentation I like. But I do find that the MSDN documentation usually gets me working, and not reading documentation much faster than others for e.g. Python, Java, JavaScript, CSS, my pedometer.
    - lacampbell 7y ago
      > Can you provide some examples of documentation you do like? MDN (Mozilla documentation for web stuff) is generally pretty good. Obnoxious colors aside, this javascript library is very easy to get started with: https://localforage.github.io/localForage/ https://localforage.github.io/localForage/
BinaryIdiot 7y ago
Hmm. When I need to find a specific JS library I do a search and there are a good 20+ of them all with different dependencies, levels of support, different past issues, etc. It's so difficult to pick a good one. I mean, you can just _pick one_ and go on with your life but if you pick the wrong one it can really bite you. Whereas with C# or Java or Ruby or Python or countless other languages the standard library is big enough that a quick search, find an example and boom I'm done (I always thought the MSDN was amazing; it's like Mozilla's JS documentation but for C# with tons of awesome examples). If it's highly complex I can find a library that likely depends mostly on standard library functions and not have to worry about tons of dependencies. I do a ton of development in JS and I think its standard library is one of its biggest flaws. ECMA would rather avoid adding too much to it as they seem to view the language as a small, scripting language and the platform should provide everything. That's a valid view, I think, but I don't agree with it at all. It's grown far too much to keep that view IMO.
dep_b 7y ago
I'm a bit out of the loop regarding C#, but I don't remember having trouble finding what I needed in .Net itself. MSDN was bad back then but StackOverflow has been an excellent resource for C# from the beginning.

I have usually found, installed and started using a good javascript library in less time than it would take me to make sense of MSDNs enterprise-soup documentation.

manigandham 7y ago

What does MSDN have to do with this? Are you talking about C# and .NET specifically? Have you seen the current documentation? https://docs.microsoft.com/en-us/ https://docs.microsoft.com/en-us/

lacampbell 7y ago
Yes, I felt brave, so I went after everyones darling C#, and not an easy target like Java. I read C# documentation several times a week. I do not like it.
- gmiller123456 7y ago
  Can you provide some examples of documentation you do like? While I can't ever remember reading some documentation and saying, "Wow, that was fun!", so I can't say there's any documentation I like. But I do find that the MSDN documentation usually gets me working, and not reading documentation much faster than others for e.g. Python, Java, JavaScript, CSS, my pedometer.
  - lacampbell 7y ago
    > Can you provide some examples of documentation you do like? MDN (Mozilla documentation for web stuff) is generally pretty good. Obnoxious colors aside, this javascript library is very easy to get started with: https://localforage.github.io/localForage/ https://localforage.github.io/localForage/

BinaryIdiot 7y ago

Hmm. When I need to find a specific JS library I do a search and there are a good 20+ of them all with different dependencies, levels of support, different past issues, etc. It's so difficult to pick a good one. I mean, you can just _pick one_ and go on with your life but if you pick the wrong one it can really bite you. Whereas with C# or Java or Ruby or Python or countless other languages the standard library is big enough that a quick search, find an example and boom I'm done (I always thought the MSDN was amazing; it's like Mozilla's JS documentation but for C# with tons of awesome examples). If it's highly complex I can find a library that likely depends mostly on standard library functions and not have to worry about tons of dependencies. I do a ton of development in JS and I think its standard library is one of its biggest flaws. ECMA would rather avoid adding too much to it as they seem to view the language as a small, scripting language and the platform should provide everything. That's a valid view, I think, but I don't agree with it at all. It's grown far too much to keep that view IMO.

dep_b 7y ago

I'm a bit out of the loop regarding C#, but I don't remember having trouble finding what I needed in .Net itself. MSDN was bad back then but StackOverflow has been an excellent resource for C# from the beginning.