Earlier quoted context omitted.
JavaScript poses a large security and privacy risk. Think browser fingerprinting, XSS, JS-based analytics, poor or missing CSP + hijacked npm modules, etc. I generally keep JS disabled as much as possible.
That's great and it's your choice to disable it but his point was don't expect developers that rely on JavaScript to power modern web experiences to develop their site to fit your strict requirements. JS does way more then just fingerprint users and open up security vulnerabilities. You're in a minority that's asking for fall-backs in a world that's so far removed from simple fixes.
So they're going to expect me to leave a major malware and privacy-invasion vector open so they can indulge in creating their 'web experiences'.
Nope. This sounds like kids playing around, not professionals working.