Not so! (well, if the concept is broken, after all it isn't due to the substance of this thread.)

Harsher than I would have said; but there is a point there.  Often on these things what happens is that people who don't know have one view of the priorities, and people in the know have another. If someone's priorities differ they need to step up--- and sometimes that does happen but once they learn more their priorities change. See also table 1: http://fc15.ifca.ai/preproceedings/bitcoin/paper_9.pdf  the greatest pain vectors of malleability can be avoided simply with careful wallet design.

In the case of BIP62 one of the reasons it has not progressed is that we haven't had enough review capacity to achieve confidence that such a broad scoping change would actually achieve its goals and not cause collateral damage-- especially because with "random pain" mostly answerable via wallet design-- the goal of it becomes making multstep contracts secure... which is something that can't be approximate.

BIP66 pulled forward part of BIP62 that was done and ready.

Folks here like int03h suggest that nothing has been done, but the opposite is true-- in terms of easily malleability on ordinary transactions, IsStandard-like-checks almost completely cover it. Every known vector of malleability has been closed off that way, except the one where common wallets still emit random forms. If we could enforce lowS as a standardness rule this issue would likely no longer be a source of intermittent annoyance for ordinary transactions. Bitcoin Core has been ready for that for roughly two years. But since we don't want a world where everyone is forced to run Bitcoin Core (much less the latest version of Bitcoin Core) reality is limited by what improvements people adopt.

People don't even need to be developers to help-- I posted a list of highS producing addresses, if we can identify more software which produces this form and get it fixed then we'll be well positioned to move forward. Why are people still whining here instead of sluthing? Come on-- I'm not even asking anyone to write code.

FWIW, virtually every cryptocurrency (including litecoin) has the same kind of issue, even some promoted as "immune to malleability"... Even most created after this issue was well understood in bitcoin have not bothered learning from it. That this property existed in Bitcoin is unfortunate but easily justifiable, that so many others have slavishly replicated  this well known poor behavior, even when the Bitcoin community knew exactly what was needed to stop it completely, is something else entirely.  My own published alternative network work, the Elements Alpha testnet sidechain, eliminated this whole class of issue in a very complete and robust way-- but its approach is not easily applied to Bitcoin because the deployment would be disruptive. Fortunately, for what people are currently complaining about nothing that complete is required.