gofpher VS lo

I'm glad to see this idea getting some traction again. I haven't used Go much in the last few years, but I started writing playing around with a similar idea back in 2016 when I was working on a small compiler for a configuration management tool, and later put together a [small stand-alone proof of concept library](https://github.com/rebeccaskinner/gofpher) as part of a [talk](https://speakerdeck.com/rebeccaskinner/monadic-error-handlin...).

At the time, I remember finding FP in go surprisingly ergonomic. Implementing the library to support it was a pain since the type system wasn't expressive enough to prevent everything from devolving into a pile of untyped reflection, but it was reasonably easy to keep that an implementation detail. On the whole, I felt like go would have lent itself well to the "dash of FP for flavor" style of programming that seems to be gaining popularity these days. Unfortunately, in 2017 at least, the Go community seemed to have very little interest in the idea.

I still have a fondness for Go. It always felt nice to use. If the language features have caught up to the point where a robust library like this is feasible, and the communities attitude has shifted, I might take another look at the language.

Monadic error handling like in ML work-alikes, Rust etc. would be a good start. Adopt:

• https://github.com/rebeccaskinner/gofpher

• https://speakerdeck.com/rebeccaskinner/monadic-error-handlin...

I've been talking to the local Go user group. No one even knows about that concept. This continues a pattern of general ignorance/lack of looking beyond one's horizon I've noticed.

Might be interesting to make a library that competes with https://github.com/samber/lo?

On the other hand, I advise you NOT to use this kind of library and write simple, fast go code most of the time, with the occasional generics helper. Why the hell would I clutter my code with, for example: https://github.com/samber/lo?tab=readme-ov-file#fromentries-...

This wasn't feasable without generics, and now with generics they're already adding some convenience functions to the stdlib, like in the slices package.

For map, reduce etc it's not in the stdlib yet, but you can use https://pkg.go.dev/github.com/samber/lo

In particular, I'd like recommend samber/lo, this is a lodash generic tool for golang.

What are some 3rd-party libraries for Go that you use often/all the time? Instead of "just implement everything yourself", I would really like to get some tips. For instance, a few days ago I discovered https://github.com/samber/lo , which looks very good if I want to have list comprehensions (Python) / LINQ methods (C#). https://pkg.go.dev/github.com/atotto/clipboard is also good for clipboard operations. What else do you suggest and for what task?

A simple alternative is the combination of:

- https://github.com/samber/lo

- https://github.com/samber/mo

The split is also nice as you can choose to just use the generic convenience functions from lo without the more FP related things from mo.

Some packages offer utilities to gather results from goroutines, such as multierror.Group or parallel.Map in samber/lo.