New in Go 1.20: wrapping multiple errors

Re:New in Go 1.20: wrapping multiple errors by lokar on Sunday December 11, 2022 @12:39PM (#33945336)

Go explicitly prioritizes productivity in large Eng orgs with a range of programmer experience. This is often at the expense of what language enthusiasts this is important/new/cool

You may not agree, but they are doing what they said they would from the start, and it’s been fairly effective.

[ Parent | on HN ]

Re:New in Go 1.20: wrapping multiple errors by hocuspocus on Sunday December 11, 2022 @06:13PM (#33948678)

Eschewing industry standard ergonomics that have been taught to every developer for the past 3 decades seems like the total opposite of "prioritizing productivity" to me.

Besides, in large engineering organisations you're always going to find multiple languages. Even at Google, which keeps a very short list of blessed languages compared to most companies, the Googlers I know who typically work on "proto to proto" middleware in Go are often jumping into codebases in Java, Kotlin, Dart or TypeScript. So clearly, they can deal with modern language features too.

[ Parent | on HN ]

Re:New in Go 1.20: wrapping multiple errors by lokar on Sunday December 11, 2022 @08:48PM (#33949901)

At google it mostly displaced uses of C++ and python

[ Parent | on HN ]

Re:New in Go 1.20: wrapping multiple errors by kaba0 on Sunday December 11, 2022 @04:05PM (#33947489)

Java has been doing that (“blue collar language”) since its inception, and is arguably doing a much better job at it.

[ Parent | on HN ]