Meta’s Microservice Architecture [pdf]

Re:Meta’s Microservice Architecture [pdf] by patmorgan23 on Tuesday July 11, 2023 @10:25AM (#36681424)

Throw is much worse than GOTO. GOTO is explicit you always know where it goes. Throw has no idea where catch is and catch has no idea where throw is. It's hidden control flow.

Go/Rust/Zig Errors as values is a much better system forcing you to explicitly deal with the error, crash or pass it on. Rather than hoping you handled all the correct exceptions/someone else will handle all of them.

[ Parent | on HN ]

Re:Meta’s Microservice Architecture [pdf] by o1y32 on Tuesday July 11, 2023 @12:08PM (#36683038)

If this were a top level comment I am sure you'll get 20 people disagree with you on this

[ Parent | on HN ]

Re:Meta’s Microservice Architecture [pdf] by randomdata on Thursday July 13, 2023 @10:03AM (#36709319)

Even Dijkstra followed up the "Go To Statement Considered Harmful" letter with the "On a Somewhat Disappointing Correspondence" letter because "20" people disagreed with him.

There will always be naysayers. The above is starting to become generally accepted, though, and modern languages are moving away from the practice just as languages moved away from unbridled gotos.

[ Parent | on HN ]