Wait until they find out how much stuff originated outside of dotnet. I recall a time when a significant portion of the dotnet community did not really venture outside of their ecosystem and were shocked to find that MS just adopted emergent or popular patterns, technologies, and technologies, as if nothing existed until MS built it[0]. The height of this attitude was before dotnet, MS, and really the proprietary software community had fully embraced open source software. I’m unsurprised to find it’s not entirely gone, but I hope it’s fast on its way out.
While it’s great for any ecosystem to adopt new technologies and techniques into their stack, it’s detrimental to think a concept doesn’t exist until your preferred vendor releases their interpretation of it. Beyond the disregard for the effort of people who created and maintain the thing originally, this myopathy also leaves a community unable to gauge the quality of the adaptation to give feedback or avoid the thing altogether. This can and has lead to walled gardens, fractured protocols and standards, poor interoperability, and stagnation in the industry. Less dramatically, you might just be missing out on stuff that’s way cooler.
While it’s great for any ecosystem to adopt new technologies and techniques into their stack, it’s detrimental to think a concept doesn’t exist until your preferred vendor releases their interpretation of it. Beyond the disregard for the effort of people who created and maintain the thing originally, this myopathy also leaves a community unable to gauge the quality of the adaptation to give feedback or avoid the thing altogether. This can and has lead to walled gardens, fractured protocols and standards, poor interoperability, and stagnation in the industry. Less dramatically, you might just be missing out on stuff that’s way cooler.
[0] https://youtu.be/J6hijsqO8H0?si=t11hHPBpd9Z2jye0