Personally I try to provide both a JS and non-JS version of any given feature--while people may no longer have K6 CPUs not everyone has an Android/iPhone either. Providing a non-JS version allows people with midgrade phones to still use all the features of the website.
That is my basic point. Don't make JavaScript a functional requirement. JavaScript should be an option. Those who do not use JavaScript should not be prohibited from enjoying the web site or contributing comments.
Regarding stability, in theory javascript should be OK. In practice the JS engine built into a given browser can leak memory quite badly--for me this manifests as having to regularly restart Firefox, which gets to be quite a nuiscance over time. TDE might end up (randomly) being the site that pushes the user's system over a memory limit, and nothing says "professional" like a site appearing to crash the users' browser.
Being in the engineering and technical fields much of my adult life, I have learned that theory and practice often don't coincide nicely. :)
I long have suspected that my low usage of JavaScript helps me avoid the common complaints about Firefox crashing and memory leaks. Who knows.
I agree that any software that crashes in itself makes a resounding statement about quality assurance and lacks a professional image. :)
Darrell