You can also optimize this a bit.
You can use Activator.CreateInstance instead of reflecting and invoking the constructor.
You can also call MethodInfo.Invoke, you don't need to create a delegate.
Also worth noting that Source Generators have replaced the need for reflection in many cases.
It's not a thing in other countries
At the end of the day if they can afford it and don't want to change you've got to ask yourself if it really matters?
I know it's silly to pay over the odds for something but it's up to them really.
Pretty much is in reality. But not literally zero, no.
I mean I've still yet to hear a reason not to use rust tbf.
But yes that's what working in a team is like.
I have to do stuff at work so I don't fuck over the frontend team. I don't throw a little tantrum about it.
Animals massively outnumber us. It's not our fault they are cowards and can't organize a rebellion properly.
"I can easily do it on my phone" is also good.
It's not a buzz word. It's the correct term.
It's when you are given 0 days notice because it's already being exploited when you find out about it.
I like using Problem detials
It's fully supported by the .net server pretty much out the box and just seems nice to stick to a standard where possible.
COVID causes long term health problems if you're unlucky.
It's not a flu it's sars and should be treated as such.
That would be the difference in cubic yard (27-1)
Here we're comparing the total volume. 27 is 27 times bigger than 1 (27 / 1)
For me you really aren't selling it.
When the answer to major draw backs with a language is use it better that's a dead end for me.
Some of the greatest programming minds have been using c for a long time and we still have a huge amount of dangerous vulnerabilities all the time.
The language is fundamentally flawed and other languages have demonstrated that you can get the same flexibility, expressiveness and performance without these flaws.
Again with the lack of many standard lib constructs. I now have to trust that every lib i use was written by a serious expert. as they'll need to implement so much themselves rather than trusting the core language team, who you hope would know it better than most.
And again with OOP. Why hack it into a language rather than use a language that supports it.
It's beginning to feel like people are just clinging to c because it's what they are used to. All I seem see are justifications of its flaws and not any reasons to actually use it.
If it came out today you'd have an incredibly hard time convincing anyone to use it over other languages.