3 ms·
> At the end of the day, you have to ask yourself about what your hourly rate is. If you are going to spend a 20 hour premium per week bandaging up a "free" .NE
by sebazzz 3y ago
> At the end of the day, you have to ask yourself about what your hourly rate is. If you are going to spend a 20 hour premium per week bandaging up a "free" .NET toolchain, whereas the official, $100/m stack costs you 1-2 hours, which one actually costs you more?
Also the official stack is supposedly supported, which means you can contact Microsoft if you have an issue.
In practice, you get some underpaid outsourced employee in the chat, who is just going to follow their script - so it is more effective to go to Visual Studio feedback or Github, depending on the issue.
- just_testing 3y agoI teach for a living, mostly people of poor backgrounds, and a lot of them in the Third World. I understand your argument (and I buy some tools myself), but I can't tell them to use paid tools because the cost may be too high in the local currency and it adds up fast.
- neonsunset 3y agoVS Code and Omnisharp are unconditionally free (and open source). DevKit and VS Community Edition are free for education scenarios. The arguments made in previous comments don’t correspond to reality.
- just_testing 3y agoThank you!! Good to know.