You're recommending that OP uses an abstraction over the system. It takes their X problem and makes it a Y problem instead (because they won't learn systems that way)!
For related examples, you can learn Ruby just by learning Rails. Or in more general aspect, the web technology stack through a modern web framework.
Though I believe it has regressed at least a bit with the introduction of DotNet Core.
Maybe it is actually better for OP to learn .net, maybe not. But the answer had quality, so I do not think the downvotes are appropriate.
There's something interesting about that; it implies that grey text signifies a non-conformist view and approach to a technical issue. As is the case here.
I like to skip to the grey text.
By contrast, it also prevents users from commenting. See dang's posts on this.
Regardless, it's interesting to note that it also, indirectly, highlights interesting comments.
Do you also find that interesting?
Thinking about it, downvoting for disagreement is the analog of upvoting for agreement.
But my point isn't to criticize anyone for downvoting. Just the opposite. It's to illustrate that thinking outside the box is in itself disagreeable, which, as is the case here, can be a searchable metric.
I am not contrarian in the sense that I think good comments are downvoted to a meaningful extent. YMMV.