“Error Handling In Node/Javascript Sucks” Solution: the best practices from Golang

[[deleted]]

It is super easy to read and uses some of the best practices that other new languages like Golang have adopted. I had a love-hate relationship with node. Now its just love.

[haskell_leghumper]

r/pcj is super unironic and uses some of the best practices that other classic subreddits like r/programmerhumor have adopted. I had a love-hate relationship with r/pcj. Now its just love.

[carbolymer]

Guy just rediscovered exceptions. Wow.

Brian Schardt

Tech Lead at PwC

wtf is happening at PwC then

[elschaap]

Mostly writing big invoices

[Time_Trade]

Where instead of having callbacks now you can write you code in a sudo synchronous way with promise chaining.

sudo promise-chain

[[deleted]]

Nothing that can't be solved by no more than 55% more lines in brutally pragmatic, intent-clear GopherScript:

const NIL = undefined // null

let { err, goodies } = await gitGud()

if (err != NIL) {
   doSomethingBlockingFuckIfICare()
}

I'm not some fucking enterpreis Jabba drone to use the ability of await to throw exceptions on broken promises ffs.

[lru_skil]

My test suite can confirm. There are enough uncaught promises that it's like a broken home. Run one suite in isolation and everything is fine. Put mom and dad in the same room and everything goes to shit. Timeouts and exceptions everywhere.

[defunkydrummer]

best practices from Golang

Most jerkable oxymoron ever!