News for hackers. Stuff that matters.
Re:Gunk: Modern front end and syntax for Protocol Buffers by grogenaut on Saturday January 19, 2019 @12:20AM (#18945486)
Not sure why I’d want to define a language independent interchange format in a language specific way and remove all of the tooling help at the same time. Why is this better? A why section/motivations would help greatly.
Re:Gunk: Modern front end and syntax for Protocol Buffers by kenshaw on Saturday January 19, 2019 @01:45AM (#18945699)
There is an explanation in the README file, but I'll explain:

It helps to standardize workflows across a number of different source repositories (all Go based), where a number of different developers had come up with different ad-hoc ways of generating code against protobuf definitions. Since the syntax is Go-derived, it reduces cognitive load for developers when specifying protocol buffer definitions. We understand that it may not be for everyone, but it works for our team.

Re:Gunk: Modern front end and syntax for Protocol Buffers by grogenaut on Saturday January 19, 2019 @01:07PM (#18948264)
Why not just make a simple go tool that just covers that issue and still uses proto thus getting the tooling and expressiveness instead.