Ignoring the really really harsh and overly rude tone.
I wonder what the difference would be if this was posted on a designer version of hackernews.
The problem with your comment is you assume everyone can dabble in everything. When you work at a big co you are hired generally to do one thing, and that's it. Designers don't touch code. Developers don't touch designs. So while Sue may be able to do CSS, JS, Cocoa but isn't allowed anymore then Bob isn't allow to open up photoshop and start "playing color the fucking button on dibbble all day long".
"The problem with your comment is you assume everyone can dabble in everything."
How is it unreasonable to assume that a designer should dabble in web development? That's hardly 'everything' and it's highly relevant to their work and goals. Frankly it's remarkable to me that web designers can still get jobs without taking the time to acquire an in-depth knowledge of the engineering stack they're designing for, even if they don't work with it on a day-to-day basis.
Designers often don't even have time to touch code, even if they could. When your organization has more trouble hiring designers than devs, you need your designers doing design 120% of the time.
Definitely, ideally you should manage your business so that all your specialists are busy doing their specialties. Designer salaries should rise if they are harder to find than devs are.
I wonder what the difference would be if this was posted on a designer version of hackernews.
The problem with your comment is you assume everyone can dabble in everything. When you work at a big co you are hired generally to do one thing, and that's it. Designers don't touch code. Developers don't touch designs. So while Sue may be able to do CSS, JS, Cocoa but isn't allowed anymore then Bob isn't allow to open up photoshop and start "playing color the fucking button on dibbble all day long".