Go: What We Got Right, What We Got Wrong

Re:Go: What We Got Right, What We Got Wrong by ysofunny on Thursday January 04, 2024 @08:54PM (#38874788)

let's just pretend that when go lang people say "systems programing" they mean smething closer to "network (systems) programming" which is where go shines the brightest

[ Parent | on HN ]

Re:Go: What We Got Right, What We Got Wrong by kernal on Thursday January 04, 2024 @10:52PM (#38875515)

And yet Google replaced the go based network stack in Fuchsia with rust for performance reasons.

[ Parent | on HN ]

Re:Go: What We Got Right, What We Got Wrong by howenterprisey on Thursday January 04, 2024 @11:41PM (#38875745)

I understand ysofunny's comment to have meant basically microservices/contemporary web backend.

[ Parent | on HN ]

Re:Go: What We Got Right, What We Got Wrong by pjmlp on Friday January 05, 2024 @03:03AM (#38876829)

After the guy responsible for it left the team.

[ Parent | on HN ]

Re:Go: What We Got Right, What We Got Wrong by ikiris on Friday January 05, 2024 @03:44AM (#38877040)

This sounds more like for perf reasons that for performance reasons.

[ Parent | on HN ]

Re:Go: What We Got Right, What We Got Wrong by kramerger on Friday January 05, 2024 @08:30AM (#38878834)

Hold on a minute.

You are confusing the network stack (as in OS development) and network applications. Go is the undisputed king of backend, but no reasonable person has ever claimed its a good choice for OS development.

[ Parent | on HN ]