lo VS functional-go

Compare lo vs functional-go and see what are their differences.

lo

đź’Ą A Lodash-style Go library based on Go 1.18+ Generics (map, filter, contains, find...) (by samber)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
lo functional-go
64 4
15,097 179
- -
6.1 5.9
10 days ago 4 months ago
Go Go
MIT License Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

lo

Posts with mentions or reviews of lo. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-06.

functional-go

Posts with mentions or reviews of functional-go. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-03-15.
  • Go 1.18 Released
    20 projects | news.ycombinator.com | 15 Mar 2022
    >> By introducing a single generic, you could reduce it from 500 lines to 20

    No one is writing 500 lines of code - just as when you use the generics syntax you don’t write the code that is generated by the compiler in response.

    You could save about 10 lines, specifically these 10:

    https://github.com/logic-building/functional-go/blob/master/...

    You would still need the comparable ~40 lines of “generic” code:

    https://github.com/logic-building/functional-go/blob/master/...

    20 projects | news.ycombinator.com | 15 Mar 2022
    earlv 17th century

    >> instead of actually giving a shit about the perspectives of those who disagree with you

    Now i resent that because i took the time to try and steelman your bad argument.

    >> they couldn't be without copy/pasting their implementation for every single array type you wanted to implement them for

    Not true, as i said there’s always been options for this:

    >> if we need them to be generic over argument types - in the absolute worst case (so not using go generate to help us here or an interface…

    Behind the scenes in the compiler, the syntactic sugar of generics are ultimately performing what you would do with “go generate“.

    >> in every project that wants to use them

    I don’t follow, why aren’t we allowed to create a library for code reuse like https://github.com/logic-building/functional-go/blob/master/... has done for example?

What are some alternatives?

When comparing lo and functional-go you can also consider the following projects:

underscore - 🌟 Useful functional programming helpers for Go

mo - 🦄 Monads and popular FP abstractions, powered by Go 1.18+ Generics (Option, Result, Either...)

go-godash - An experimental generic functional utility library inspired by Lodash

fp-go - fp-go is a collection of Functional Programming helpers powered by Golang 1.18+ generics.

fpGo - Monad, Functional Programming features for Golang

go-generic-optional - Implementation of Optionals in Go using Generics

pie - 🍕 Enjoy a slice! A utility library for dealing with slices and maps that focuses on type safety and performance.

gofp - A super simple Lodash like utility library with essential functions that empowers the development in Go

goterators - A utility library that supports aggregate & transforms functions Go with generic. Such as filter, map, reduce, find, exist

fuego - Functional Experiment in Golang

slicesol

valor - Go option and result types that optionally contain a value