News for hackers. Stuff that matters.
Re:Show HN: Nothing.js – A chainable mock object which alway... by TheAceOfHearts on Saturday March 31, 2018 @06:14PM (#16725440)
I think this kind of access pattern is typically a code smell. Instead of carrying around arbitrarily nested values you should try to normalize it into a known and consistent shape when crossing serialization boundaries.

Proxy pays a big performance penalty, and I doubt it'll be improving any time soon. In addition, I believe it's not possible to polyfill Proxy. An alternative could be to just wrap the deep property access in a try/catch:

    function getQux (input) {
      try {
        return input.foo.bar.baz.qux()
      } catch (e) {
        return null
      }
    }
Re:Show HN: Nothing.js – A chainable mock object which alway... by afranchuk on Saturday March 31, 2018 @08:12PM (#16725901)
Yeah, my first thought when seeing that it uses Symbol and Proxy was that Proxy can't be polyfilled. But it looks like there's partial polyfills for it: https://www.google.com/url?sa=t&source=web&rct=j&url=https:/...
Re:Show HN: Nothing.js – A chainable mock object which alway... by slmgc on Saturday March 31, 2018 @07:37PM (#16725768)
Wrapping you code into a try/catch block decreases performance even more, you don't want to do that. You might want to check it out: https://github.com/GoogleChrome/proxy-polyfill