Link to the uber report? Could not find it (unless it is this: https://www.uber.com/us/en/blog/data-race-patterns-in-go/)

▲

nperez19 9 hours ago | parent | next [-]

This is the actual link to the academic paper (https://arxiv.org/pdf/2204.00764)

▲

wredcoll 7 hours ago | parent [-]

Just reading the abstract, it talks about finding a number of bugs (across millions of lines of code) but I didn't see any claims that there would be fewer bugs in a different language.

Go obviously does not stop you from writing buggy code. Neither does rust or zig or whatever. Does go make it more likely to have bugs? Or a specific class of bug? Like, the real world is about trade offs.

▲

mac-mc 3 hours ago | parent [-]

Uber has fairly large golang and java codebases so they have more of an apple to apples comparison here since they are both GC languages of a similar performance class. And if a large population tends to make more mistakes with 200hp sedan A vs 200hp sedan B, there is probably something up with the design of sedan A.

	▲	wredcoll 2 hours ago \| parent [-]
		I agree, but does that study claim there are more errors per line/function/whatever in golang than java?

▲

pstuart an hour ago | parent | prev [-]

That article is meh. All of those issues are either addressed or junior programmer mistakes.

Yes, it's a bit of blame the user which will likely get the retort of "but I thought Go was perfect for junior engineers?"

Yes, there are footguns but none of the points therein were compelling.