[bitwize]

It doesn't matter what Microsoft did. As a programmer imparting knowledge in a public forum, you have a duty to be professional and state your case or air your grievances in a civilized way. What Casey did was unprofessional and toxic.

[AnIdiotOnTheNet]

I'll grant it might have been unprofessional, but we're also talking about Casey's personal twitter and his personal project that he streams to the world for free.

I guess I come from a different culture/generation, where if someone is doing as badly at their jobs as a lot of people at Microsoft are right now, then it is acceptable to call them out on it. I mean christ, we live in a world where it's ok to fire people expressing a mildly controversial opinion at work when asked to do so , or over tweets they made in the distant past that they've long since apologized for, but we have to treat people who are really crap at their jobs with kid gloves?

[okatsu]

Yup it's his personal Twitter. No one was contesting his right to post whatever he wants. But as soon as you're trying to address an audience it comes with certain responsibilities. You're free to ignore these of course but then don't be surprised if you get backlash or if new people don't listen.

I'm not really sure why you need to equate being civilized with wearing kid gloves? Is it hard for you to not call people stupid when addressing an audience? Or rather, if you do, does it help? You can call people stupid all you like in private but if you want to educate developers on how to do better I'm not sure why you're so intent on going down this route.

People also often try to make this a generational thing and blame silly emotional millenials but not attacking individuals isn't a brand new concept. And until people stop buying Windows and VS licenses en masse these people have no real reason to worry over their job and thus no real reason to listen to personal insults.