>> why do you think Go is better compared to other languages?
reply> I didn't say that. :)
I call this the Go paradox.
I simultaneously believe we should reach for it 80% of the time to solve common collaborative problems. And being a poorer language is actually an asset in these cases.
However, in doing so, we get rusty lose our fluency in more expressive, perhaps even better languages.
> Like I said - reports from users.
replyHow does that work? Are they generating the same project in different languages and comparing the results? What does it mean for the code to be "better"?
Ah, I see. I misunderstood.Is the report from an internal source, so it can't be shared? If not, I'd appreciate it if you could send me a link so I can look into it too.
replyit’s probably just some informal Slack messages between colleagues that is being described as “reports from users”. There is no Report here
replyYes, this. =) I talk to Go users around the company all the time. Their feedback has been in this direction for a bit now.
replyBut isn't this expected from users that like a certain language? Won't you also hear this response from Rust users that like Rust?
replyExactly. I only count opinions from people who have deeply used the two langs they're comparing and can express what exactly was wrong with one of them for their task.
replyYou are being downvoted but I think this is correct. I doubt Netflix is really doing a double blind RCT on which languages produce better AI pull requests. How would that even work, have two versions of each service in different languages?
replyIt's anecdata and maybe, MAYBE, a spreadsheet. Or a Google Form somewhere.