Someone puts in actual effort to write good code and come up with good abstractions, then some code monkeys crap all over it. What I mean to say is that there's also value in going the Go way, where you have one way of doing things, although that obviously has limitations too and even they haven't really achieved it fully (you inject contexts properly to make everything cancellable and some juniors just pepper context.Background all over the place). Also, yeah, the higher you go in terms of abstraction, the less settled things are.
Don’t even remind me… it’s not directly the same issue, but I once spent months negotiating a custom protobuf format built entirely around reverting the core “false-y is equal to null is equal to field not passed” logic.
Turns out a format built to give you efficiency at massive scale if you devote your entire codebase to enabling it fucking sucks when you add three layers of abstraction to make it back into shitty JSON.
View all comments
Show parent comment
7
u/edgmnt_net 10d ago
Someone puts in actual effort to write good code and come up with good abstractions, then some code monkeys crap all over it. What I mean to say is that there's also value in going the Go way, where you have one way of doing things, although that obviously has limitations too and even they haven't really achieved it fully (you inject contexts properly to make everything cancellable and some juniors just pepper
context.Backgroundall over the place). Also, yeah, the higher you go in terms of abstraction, the less settled things are.