rockerest’s avatarrockerest’s Twitter Archive—№ 20,426

            1. try/catch as standard branch handling is a huge red flag. If there's output that causes some other logic to happen, why is that an Exception? Isn't that just operation of your application? I want async/await but without the semantics that read "I didn't plan for this sad path."
          1. …in reply to @rockerest
            Like, Promises aren't perfect, but .then().catch().finally() is _pretty good_ and it doesn't require either a pyramid of doom or that I flatten a pyramid of doom into pages of top level try/catch with a little winky face at the bottom and the comment...
        1. …in reply to @rockerest
          "// this could have been a Promise chain, but FUCK YOU, I wanted to use await"
      1. …in reply to @rockerest
        And if you're like "But async/await removes the pyramid of doom, you don't know what you're talking about, it's so much better." Think again nerd: - stackoverflow.com/a/53057776 - stackoverflow.com/a/54291660
        OpenGraph image for stackoverflow.com/a/53057776OpenGraph image for stackoverflow.com/a/54291660
    1. …in reply to @rockerest
      I am slowly being radicalized by basically all new JS syntax sugar. My latest suspicion is that async/await is strictly worse than Promise and you shouldn't use it under any circumstances.
  1. …in reply to @rockerest
    Sometimes this number is below 1% and I consider wiping out class entirely, but then I run it again and it's like 55%. functional-web-components.netlify.app/
    OpenGraph image for functional-web-components.netlify.app/