If Not SPAs, What?

Re:If Not SPAs, What? by brendanmc6 on Thursday October 29, 2020 @12:22AM (#24927185)

I hear this so often, so as an exclusively js/ts dev I have to ask... what about this is “done poorly”?

```

try {

  return await fetch(url);

} catch (e) {

  handleError(e)

}

```

Because that (metaphorically speaking) is 90% of what I write. Throw in the occasional closure, `map()` or `reduce()`

My day to day headaches are never from TS, and always from unpredictable DOM api/layout/style behavior.

I guess I just don’t have any frame of reference for how “nice” a language can be. Is it just that JS has so many “bad parts” and footguns that I’ve gotten good at ignoring?

[ Parent | on HN ]

Re:If Not SPAs, What? by tofuahdude on Thursday October 29, 2020 @01:40AM (#24927611)

Fyi return await is redundant and is just creating one additional callback you didn't need (b/c you will have to call this function with an await anyways)

[ Parent | on HN ]

Re:If Not SPAs, What? by chain-- on Thursday October 29, 2020 @04:50AM (#24928463)

Try / catch is the exception, if you don't await then your catch handler won't work. https://jakearchibald.com/2017/await-vs-return-vs-return-awa...

[ Parent | on HN ]

Re:If Not SPAs, What? by azhu on Thursday October 29, 2020 @04:07PM (#24935090)

Semi funny that this exchange is kinda like proof of why JS catches the hate it does.

[ Parent | on HN ]