vcsync VS lo

In terms of proliferating open source I think that statement is fair. spf13 is like brand name in open source.

I recall years back on GitHub, spf13 was like a named you were guaranteed to come across if you were sinking your teeth into go. I ended up using cast / viper: https://github.com/tony/vcsync/commit/a76681b. (Not that I'm anything special at golang)

There is, in fact a Lodash-like package for Go: https://github.com/samber/lo

What's really maps and filters? All I see is loops hidden in JavaScript runtime with different names but yes, it doesn't hurt to write few readable Go code for every project, when I started Go I used something like Samber/lo this is a worthy competitor you can install in every project and make use of it😜, another thing is: you have pure go code (no type definitions) so you can easily jump right into the code to see how it's done and learn

This library is useful even in testing https://github.com/samber/lo

If you are curious, try looking at github.com/samber/lo and github.com/samber/mo packages if you get a chance.

mostly this https://github.com/samber/lo

Any different then what is provided by https://github.com/samber/lo?

otherwise this library has some success for some operations: https://github.com/samber/lo - it's a bit of tooling around searching/filtering and such, you'll need to dig a bit more if you need vecdeque, heaptree and such.

case in point, lo

I rarely implement generic struct or method my own. But i use https://github.com/samber/lo quite a lot for slice/map manipulation.