4 ms·
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) {
by brendanmc6 6y ago
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?
- tofuahdude 6y agoFyi 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)
- chain-- 6y agoTry / 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-await/ https://jakearchibald.com/2017/await-vs-return-vs-return-awa...
- azhu 6y agoSemi funny that this exchange is kinda like proof of why JS catches the hate it does.