News for hackers. Stuff that matters.
Re:The optional chaining operator, “modern” browsers, and my... by pier25 on Tuesday January 11, 2022 @03:34PM (#29897438)
Exactly.

The cost to make a website accessible to everyone is so high that it really only makes sense for critical websites.

Re:The optional chaining operator, “modern” browsers, and my... by bmeski on Tuesday January 11, 2022 @03:48PM (#29897623)
It’s really not if you simply stick to html, css, and a tiny bit of js on the client.
Re:The optional chaining operator, “modern” browsers, and my... by pier25 on Tuesday January 11, 2022 @08:06PM (#29900966)
Unfortunately that approach doesn't work for many (most?) use cases.
Re:The optional chaining operator, “modern” browsers, and my... by bmeski on Tuesday January 11, 2022 @08:23PM (#29901119)
What?

They are literally the 3 client “languages” of the web.

Everything your abstractions/frameworks do is produce html, css, and js.

Re:The optional chaining operator, “modern” browsers, and my... by pier25 on Tuesday January 11, 2022 @10:17PM (#29901855)
What does that even mean?