3 ms·
>.NET has been held down by the image of its early days, I have been in .NET since 2009. I don't what would lead anyone to replace Go with .NET? That seems lik
by whoknowsidont 3y ago
>.NET has been held down by the image of its early days,
I have been in .NET since 2009. I don't what would lead anyone to replace Go with .NET? That seems like it's asking for a lot of problems you previously did not have.
Can you expound on your decision?