"I have yet to be cited a single good example here - very often what is being done would work just fine in HTML, with less overhead, but the 'designers' just do not understand HTML, or have any desire to learn it, so they do things this way instead." Over the years, I've done a lot of work with games and simulations for training. Often times, these training simulations must coexist with existing talent management infrastructure. This means a JavaScript API for communicating performance data to the host platform. I will concede that this could be handled in other ways, but they would most certainly be clunkier, slower, and more prone to error. But what about the simulations themselves? In one example, we built an electrostatic puzzle game in which students had to charge robot parts using charge sharing, conduction, induction, and the triboelectric effect in order to obtain target values. Each manipulation (e.g., sharing charge by physically connecting two charged objects with a wire) produced a change in state that was manifest in the underlying data model and on screen appearance. We could not have produced this educational game with just HTML.

While I understand some the sentiment expressed here, a lot of this nonsense. An HTML-only web is great for relatively static content, but not so great for anything much beyond that. Is it so difficult to grok why you might want content to change on the client? I don't think so. Is JavaScript used for nefarious purposes? Yes, all the time. Is there bad UX because of JavaScript? No doubt. It is, however, a useful tool in the hands of skilled designers and developers. I'm usually the one telling people to get off the lawn, but in this case, meh whatever.

SSNs, like passwords, need to die. They are a relic that doesn't work anymore.

There are many reasons to keep a particular job - money is but one. In a discussion about work - life balance, this seems to be a pretty important point.

from the last Neal Stephenson trilogy.