3 ms·
the best TLDR I've seen of this philosophy is - if you find yourself writing all over your codebase try { ... } catch (e) { console.log(e) } then you shou
by kbyatnal 4y ago
the best TLDR I've seen of this philosophy is - if you find yourself writing all over your codebase
try {
...
} catch (e) {
console.log(e)
}
then you should probably just "let it fail" since you can't actually handle the error
- deleted 4y ago[deleted]
- charcircuit 4y agoThat construction adds a layer of "let it fail." For example you might want to have your web server be able to mark a connection as failed instead of only being able to mark the entire server as having failed.
- anupamchugh 4y agoThat's impressive!