a[low:high:max] in Golang – A Rare Slice Trick

Re:a[low:high:max] in Golang – A Rare Slice Trick by Groxx on Saturday March 18, 2023 @02:32PM (#35211790)

"X for me but not for thee" is very much the vibe Go gives me, yeah.

I mean, I have completely replaced my adhoc Python use with it and I'm much happier. But it's terrifying to use to build large systems.

[ Parent | on HN ]

Re:a[low:high:max] in Golang – A Rare Slice Trick by ikiris on Saturday March 18, 2023 @03:43PM (#35212414)

Part of it is that "large systems" are almost all combinations of small systems with proto boundaries, so it's not much of an actual risk unless you're making giant monolith code.

[ Parent | on HN ]

Re:a[low:high:max] in Golang – A Rare Slice Trick by andrewflnr on Saturday March 18, 2023 @06:30PM (#35213804)

"Proto" meaning protobuffers?

[ Parent | on HN ]

Re:a[low:high:max] in Golang – A Rare Slice Trick by konart on Sunday March 19, 2023 @03:20AM (#35216785)

I think it rather "communication via some protocol" in general.

In other words if we are not talking about giant monolith - we have N small systems to begin with.

[ Parent | on HN ]

Re:a[low:high:max] in Golang – A Rare Slice Trick by ikiris on Sunday March 19, 2023 @04:36PM (#35223300)

I meant specifically protobuffers in that case, but sure, that works.

[ Parent | on HN ]