> I'm not sure I understand why designers should know CS. Most of them spend their time in Photoshop/Sketch, not programming. Unless I misunderstand.
They also write a lot of JS and CSS that face the web. I didn't want to say that they should learn/know CS, but just some basics of computing, if they're going to write code that runs on others' machines (JS).
> Also from your other comment you would like Ajax to not be used in websites?
I would like the normal behaviour of browser widgets (links, buttons, forms) let alone. New widgets are OK with me, e.g. an interactive map, a carousel, a dropdown menu. You get to define the behaviour of these tools, but a button, a link etc. has an associated meaning with them.
Really? I've never met a designer that wrote js. Engineers should be writing the software. Js web apps are essentially the same as c++ win32 ( or whatever thick client side tech ) apps with some web semantics like urls preserved. I've seen designers write css, and I think the good ones do, but I've never met one that was happy to or was particularly skilled at it.
There is a recent inclination among designers to write JS and take part in writing front-end code. Youtube is full of their talks.
JS/Hypertext was not initially meant for engineering anyting, so it's not analogous to a combination of UI toolkit & proper programming language & a compiler.
Because otherwise you get a lot of designers who know print design but don't actually know how a web page works on a technical level. That gives you awkward (or flat out impossible to implement) designs that were made without any regards to how it actually works in a browser across various screen sizes and devices.
Also from your other comment you would like Ajax to not be used in websites?