Re:New in Go 1.20: wrapping multiple errors
by bamboozled on Sunday December 11, 2022 @09:20AM
(#33943420)
Sorry, but what are you talking about? Poorly designed? A lot of incredibly good software is written in Golang and while that might not mean it's the best language ever designed, it would be hard to say it's "poorly designed" based on that fact alone?
[ Parent
| on HN ]
Re:New in Go 1.20: wrapping multiple errors
by shakow on Sunday December 11, 2022 @09:51AM
(#33943663)
Incredibly good software has been written in JS, that does not make a good language out of it.
To a competent team, a bad language is an hindrance, not a deadly obstacle.
Re:New in Go 1.20: wrapping multiple errors
by sethammons on Sunday December 11, 2022 @10:55AM
(#33944230)
The difference is options. Developers can use anything on the back. You are stuck with JS on the front. That devs _choose_ Go means something.
Re:New in Go 1.20: wrapping multiple errors
by za3faran on Sunday December 11, 2022 @03:39PM
(#33947232)
You'd be surprised that the answer in a lot of times cooties just be hype or inertia. I've seen it first hand at an employer that supported both Java and golang. A new project was started in golang just because of inertia, whereas Java would have been a strictly superior choice on basically every front. The resulting code base was a huge mess, even as per the admission of the "lead" who made the original decision, who clearly had no business making that decision in the first place. Literally over a million dollars spent on a mediocre, unmaintainable result
Re:New in Go 1.20: wrapping multiple errors
by bamboozled on Sunday December 11, 2022 @10:23AM
(#33943915)
So then it's just a subjective statement because whether or not you think the "design" is good, it's design is obviously practical, well liked and in heavy use?