3 ms·

I think the basic problem boils down to this: poorly (or completely lacking) version and dependency references in external documentation. That is, blogs, Stack

by ethbr0 5y ago

I think the basic problem boils down to this: poorly (or completely lacking) version and dependency references in external documentation. That is, blogs, Stack Overflow, code examples, etc. Most of that is the fault of authors, but presumably you don't want a 20 year .NET veteran to be the only person capable of writing a complete "Hello World"? As a consequence, the new developer experience feels like the bad old Java days of "Oh, you want too foo? Well, that tutorial is built using the bar framework, which is incompatible with the nubar libraries you have on your machine." Agree with another comment here that Microsoft needs to clearly cut legacy off + rename, in order to have a future.

torginus 5y ago
That's a weird perception - in my experience, .NET APIs have largely remained stable, at least when going back like half a decade. It's nothing compared to the node ecosystem, where yearly breaking changes are common, and looking at ta 5+ year old project, you'll see that the popular libraries for every problem used to be different.
animal531 5y ago
This isn't remotely true. Any person that has learned for example C/C++ can be productive in a week of having picked up C#. At the start you can just translate all the basic C constructs such as classes/structs/methods/for loops/ifs etc. to their C# version (which is extremely similar in nature). After that you can add C# specifics such as LINQ etc, but it's not necessary to be proficient in the language. Online snippets of anything you search for invariably just works, I've never had an issue of something being outdated.
jmnicolas 5y ago
I don't get where you're coming from: last week I upgraded a WPF .net 4.6 project (probably from 2017) to .net 6 without a glitch except of course the things I wanted to change (I moved all database calls to Dapper), while reopening a very simple Flutter project made in January this year I find a few deprecated things that needs to be corrected.

by ethbr0 5y ago

torginus 5y ago

That's a weird perception - in my experience, .NET APIs have largely remained stable, at least when going back like half a decade. It's nothing compared to the node ecosystem, where yearly breaking changes are common, and looking at ta 5+ year old project, you'll see that the popular libraries for every problem used to be different.

animal531 5y ago

This isn't remotely true. Any person that has learned for example C/C++ can be productive in a week of having picked up C#. At the start you can just translate all the basic C constructs such as classes/structs/methods/for loops/ifs etc. to their C# version (which is extremely similar in nature). After that you can add C# specifics such as LINQ etc, but it's not necessary to be proficient in the language. Online snippets of anything you search for invariably just works, I've never had an issue of something being outdated.

jmnicolas 5y ago

I don't get where you're coming from: last week I upgraded a WPF .net 4.6 project (probably from 2017) to .net 6 without a glitch except of course the things I wanted to change (I moved all database calls to Dapper), while reopening a very simple Flutter project made in January this year I find a few deprecated things that needs to be corrected.