yosh

@jaffathecake but that leaves me in a rhetorical deadlock. Truth is, functions are the most convenient, low level way of accessing most APIs

@yoshuawuyts agreed. I'm still missing something here. No one's saying fetch() should stop being a function.

@jaffathecake wait, is all of this all a big misunderstanding? Are you saying I can use fetch / SW without promises & implicit catch?

@yoshuawuyts when you say function, do you mean callback? Because fetch() is a function, whereas in fetch(url).then(fb), fb is a callback

@jaffathecake but fb is a callback with a try catch wrapped around it, which is the thing I'm most unhappy about. I can live with the rest

@yoshuawuyts the whole execution context has a try/catch wrapped around it. A JS error does not cause a tab to crash.

@jaffathecake again: why does Fetch need to decide this for me? If I want to crash my tabs, let me have an option to do that.

@yoshuawuyts fetch has also decided for you that it should be spelled f-e-t-c-h. And also, no, you may not crash tabs.