Thanks Konstantin, This is the kind of feedback I was looking for! I forgot to include the link to my github repo in my original post (did you find it anyway?) so I'm not sure if you read my README. I took a look at sqlx before writing sqlez, and while sqlx is a great improvement over the basic sql package, I thought it could be simplified even further and decided to write sqlez. The goal I had was to allow the user to just pass structs back and forth, without any need for further preparation before passing those structs to/from other parts of their program. I couldn't think of a succinct way to explain that, which is why I chose to include a lot of code examples.
I will re-write my README with what you said in mind (remove the "marketing", which was supposed to be mostly a joke anyway :), and explain how it relates to other options). Here's the repo just in case: https://github.com/jmacwhyte/sqlez On Sunday, March 5, 2017 at 6:10:26 AM UTC-8, Konstantin Khomoutov wrote: > > On Sun, 5 Mar 2017 12:42:24 +0200 > Janne Snabb <sn...@epipe.com <javascript:>> wrote: > > > > After seeing a need for simplifying SQL databases in Go, I have > > > written a new package that makes it very easy to do basic SELECT, > > > INSERT, and UPDATE database operations. Essentially you define a > > > struct that corresponds with the data in your database, and then > > > you can simply pass that struct to my package to insert and > > > retrieve data. I'm now using it in one of my projects, and it has > > > reduced database-related code by 60%, making things much more > > > readable! > > Looks similar to https://github.com/jmoiron/sqlx which is well > > established. Might be a good idea to add a short summary of > > differences/additional benefits compared to sqlx in README. > > I concur. [1] has a pretty incomplete (a popular package sqlx is > missing) but a sizeable list of ORM projects, and [2] yields lots of > stuff, too. > > Go is a natural pick for a certain kind of projects. One of these > kinds is a "typical webapp"; since webapps require state persistence, > they need databases, and this leads to Go enjoing true proliferation > of "web frameworks" and "SQL ORMs". > > What I'm leading to is that while it's nice to see your excitement > about Go and stuff you can do with it, I'm afraid it's hard to make > anyone who use Go for some time immediately excited with a piece of > news about a new web framework or an SQL ORM. ;-) > > So instead of marketing propaganda, it would be cool to see comparisons > with the so-called "prior works". That would surely be less shiny but > would indicate that you have actually researched what's already there, > identified the weak spots, and fixed at least some of the shortcomings > of the existing packages. > > To explain all that from another PoV, consider the following. > While competition is a great thing, it tends to produce lots of > half-backed (and then usually abandoned by their sole authors) stuff. > So, say, we use sqlx in two our $dayjob projects. I reserve that sqlEZ > might indeed be better in some areas but the statement "he easiest way > to use a SQL database" is not a convincing statement for us to > consider switching or even spending time researching -- simply because > it's marketing, and thanks to omnipresent commercials, those of us who > wasn't living on a deserted rock for the last couple of decades learned > not to trust slogans blindly ;-) We'd like to see hard facts instead. > Hope you'll understand. > > 1. https://github.com/golang/go/wiki/Projects#orm > 2. https://godoc.org/?q=sql > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
