AAaarondl0·Dec 15, 2016
I want to see the Go community and it's libraries flourish. But having libraries like this around which provide extra confusing and probably poorly maintained choices for users is detrimental to it's overall health. There's already great examples of maintenance rot found even amongst the very popular libraries like go-yaml and httprouter.
One thing you can say about Go is it has 1000 Micro-frameworks, ORMs, Routers, and Logging libraries. Most of them are within a percent of giving the exact same feature set with the exact same approach and and ever so slightly different API. Lots of them share the same mistakes as they are a user's first project or a learning arena (though routing has been a pretty benchmarked area so that's been better than the others).
As someone who has open source libraries, and who uses Go in their day job and at ho
Read the rest
me my personal opinion is that Go needs fewer, stronger libraries. Well supported, well maintained pieces rather than this illusion of choice that's presented today. I'm sorry if I came off as crass in my reply to the OP but that's simply the state I see in the community today.
Ideally there'd be 2-4 ORMs in Go that would be the goto. And half would use a code-generation approach, half would use the reflection based approach.
https://github.com/astaxie/beego/tree/master/orm
https://github.com/cosiner/gomodel
https://github.com/jinzhu/gorm
https://github.com/go-gorp/gorp
https://github.com/coocood/qbs
https://github.com/go-reform/reform
https://github.com/vattle/sqlboiler
https://github.com/upper/db
https://github.com/astaxie/beedb
https://github.com/naoina/genmai
https://github.com/monochromegane/argen
https://github.com/square/squalor
https://github.com/theduke/go-dukedb
https://github.com/dropbox/godropbox/tree/master/database/sq...
(...and more)
And now: https://github.com/samonzeweb/godb
Do we truly need this? This one in particular feels a lot like upperdb. And if it's for learning only, don't publish it to things like hackers news which makes people seem like it's something you should use as opposed to the more mature libraries out there. This is what I meant by fragmentation, it's an illusion of choice. There are actually very few logging/routing/orm/micro-framework libraries you should really use if you're serious about a project.