News for hackers. Stuff that matters.
Re:The ups and downs of porting 50k lines of C++ to Go (2015) by petersellers on Thursday March 14, 2019 @02:46AM (#19386984)
>Go pretty much ate the lunch of C# and Java when it comes to backends and devops

Are you saying that Go is significantly more popular than Java for backend, server-side development? I'd like to see a citation on that, because pretty much any statistic I've read has said otherwise. If you are saying it's significantly more performant, then I'd like to see evidence for that too.

Re:The ups and downs of porting 50k lines of C++ to Go (2015) by ilovecaching on Thursday March 14, 2019 @03:14AM (#19387097)
Benchmarking is error prone, and so are language statistics. Certainly Go has had a meteoric rise and much of the big innovations are happening in Go (Kubernetes, Docker, Prometheus, Terraform).

Go is simple, easy to install, and the benifits of a compiled language are huge. I can apply all of my systems knowledge to understand how my app is performing. The JVM is a career in of itself, and locks you into an ecosystem that is very proprietary and frankly full of lame enterprise salesmen and big business fogies. Go is fun. It’s branding is fun, it’s community is passionate, and a lot of big names are on the tin that speaks to a lot of us who love and grew up on Unix.

I mean, do you want to support Oracle and Larry’s bid to buy more islands or ken and rob?

Re:The ups and downs of porting 50k lines of C++ to Go (2015) by blub on Thursday March 14, 2019 @05:21AM (#19387617)
Compared to passionate comunities, fun and evil CEO arguments, benchmarking and language statistics are not error prone.

You're not really arguing in good faith. This reads more like a parody.

Re:The ups and downs of porting 50k lines of C++ to Go (2015) by igouy on Thursday March 14, 2019 @10:13AM (#19389354)
> Benchmarking is error prone, and so are language statistics.

… and so is just saying stuff :-)