But how do you give the designer the opportunity to "sketch" but also describe relationships and constraints? You could use code, but then the designer is then also a de-facto developer. And having to consider relationships and constraints too much can lead to those considerations dictating the design, rather than the other way around.
And the main reason why is that the designer is only capable of thinking in their toolset, which happens to usually be photoshop. PS simply doesn't cut it dealing with the complexity of web applications in all the different form factors it needs to work on. This has lead me to believe that if you're a web designer, your medium is HTML/CSS and potentially JS. So you should understand and be fluent in it. The designer is responsible for actually building out the html templates/styling used, and the developer is responsible for bringing those to life, but each has a lot of input at every step. A lot of crossover builds better projects :)
To the average designer (and almost anyone else) these distinctions don't exist - if you write "code" or something that looks like math, its programming.
There will always be a place for people who want pixel perfection. I think that place is called print. Eventually, we're going to let go of the idea that we control layouts at the concrete level (as opposed to a more semantic level, i.e. describing relationships and constraints), but that future is harder to see.