News for hackers. Stuff that matters.

A comment on The ups and downs of porting 50k lines of C++ to Go (2015). Parent comment

Re:The ups and downs of porting 50k lines of C++ to Go (2015) by ilovecaching on Thursday March 14, 2019 @03:16AM (#19387108)
In some ways Go is a litmus test. Do you have a simple, consistent schema? Are you trying to overload the types of fields and making parsing more difficult? I have run into this problem myself, but I realized that Go was pushing me to simplify and make things uniform which actually made my life way easier in the long run.
[ Parent | on HN ]
Re:The ups and downs of porting 50k lines of C++ to Go (2015) by jcelerier on Thursday March 14, 2019 @07:26AM (#19388233)
nice, I'm just going to send mails to the various creators of the JSONs I consume to ask them to change their protocols because it's not simple enough and solve world hunger while I'm at it
[ Parent | on HN ]
Re:The ups and downs of porting 50k lines of C++ to Go (2015) by stock_toaster on Thursday March 14, 2019 @04:26AM (#19387377)
Most of my struggles here have been when consuming /existing/ json blobs, specified elsewhere: 3rd parties, other internal services, "versioned" json blobs, and the big one... consuming json structured logging.

So I think we could both be right.

[ Parent | on HN ]