3 ms·
This reminds me of an ongoing discussion I was having with friends about Golang web frameworks -- one side of the argument is that you can achieve so much with
by rcarmo 9y ago
This reminds me of an ongoing discussion I was having with friends about Golang web frameworks -- one side of the argument is that you can achieve so much with the standard library that frameworks are "unnecessary", but folk like me want an ORM(ish) layer and some kind of back-office scaffolding.
https://beego.me https://beego.me and https://iris-go.com https://iris-go.com are nice, but we (all) have (as yet) to find a Django-like framework that comes with an extensible back-office.
So... Any pointers on the latter? I can do an Ask HN, but this seems like a good context to ask in.
(Edited to add: why the downvotes? Is this not a legitimate question?)
- bracki 9y agoYou might want to give https://getqor.com https://getqor.com a try.
- e12e 9y agoI'd argue that what you probably want in a new project (possibly with legacy db), is a graphql wrapper for your db, and a single-page js app (react/vue/elm/etc.) front-end. Which means the server side would need a way to wrap the db for graphql (along with a way to set up authorization), and the front-end would need to be able to discover/generate the crud parts. If you really want a "legacy"/"traditional" framework (fat appserver handling form input, rendering html, talking to db backend), I think the mature ones will be hard to beat (eg: django).
- nishs 9y agoIris is a poorly maintained project that I would not recommend for production use. See the drama unfold at https://www.reddit.com/r/golang/comments/57w79c/why_you_really_should_stop_using_iris/ https://www.reddit.com/r/golang/comments/57w79c/why_you_real... and https://www.reddit.com/r/golang/comments/57tmp1/why_you_should_not_use_iris_for_your_go_projects/ https://www.reddit.com/r/golang/comments/57tmp1/why_you_shou...
- rcarmo 9y agoWell, it _seemed_ nice. Regardless, I'm a bit more concerned with back-office scaffoldings myself. Any pointers?
- golangnews 9y agoI wrote a scaffold generator here you may find interesting. https://github.com/fragmenta/fragmenta https://github.com/fragmenta/fragmenta It’s fairly simple to write some simple generator using the built in text/template package if all you want are admin scaffolds.
- iris-go 9y agoNote the dates and you'll see the truth, if you're a programmer you can also read the code, Iris doesn't even use the libraries the 1+ year old article claims to be used there.
- iris-go 9y agoThis is totally propaganda, they spamm those links without even reading the code. Florin is clearly putting lies to a part of the community to deflame the Iris via the slack golang chat. He's also banned the author of the web framework without notice or any other action from his behalf. Is this a healthy relation between an author of a popular software and a guy who never wrote a single line of code?
- nishs 9y agoRather than use a full-fledged framework, I would recommend combining orthogonal packages such as - julienschmidt/httprouter [1] for routing, - jmoiron/sqlx [2] for SQL access, and - gorilla/websocket [3] for websockets sqlx isn't an ORM; it's more a convenience wrapper around the standard library's database/sql package. gorm is the nicest ORM I've found, but I think even the well-written ORM packages are unnatural to use because of restrictions in Go's type system. (Sorry if this isn't the kind of answer you were hoping for.) [1] https://github.com/julienschmidt/httprouter https://github.com/julienschmidt/httprouter [2] https://github.com/jmoiron/sqlx https://github.com/jmoiron/sqlx [3] https://github.com/gorilla/websocket https://github.com/gorilla/websocket
- bsaul 9y agoI regularly go down this road with go. My conclusion is that it's never going to suit that use case. I'm not even sure it's not technically doable (i think introspection and interface{} can go quite far), but it's just culturally opposed to this kind of project. People like go for its minimalist approach. Not in the sense that you don't have a lot of code to write, but more in the sense that you are in control of everything that happens, and that you can read an understand every part of your codebase. ORMs , code gen, magic wrappers, etc is something that people in that community just hate.
- rcarmo 9y agoI understand that, which is why I said "ORM(ish)". But a back-office scaffolding would go a long way to move some of us off of Django.
- y4mi 9y agoWhy do you want to move off of Django?
- rcarmo 9y agoBecause we're all using Go for other projects (even if piecemeal) and would like to build the entire project in a single language.
- bsaul 9y agoi personaly only would use go for very technical, low-level middlewares (as in, just above the OS layer) involving networks. The good side to it being simple to understand and maintain is that you won't pay a lot of debt if you're adding it to your stack. There isn't a single language that fits all use case perfectly anyway, so we'd have to just go to the "best tool for the job" approach in the meantime.
- sd8dgf8ds8g8dsg 9y ago
- grajaganDev 9y agoI really like Goa: https://github.com/goadesign/goa https://github.com/goadesign/goa - it has integration with Gorm via Gorma: https://github.com/goadesign/gorma https://github.com/goadesign/gorma
- konart 9y agoLook into https://github.com/markbates/pop https://github.com/markbates/pop
- tacticus 9y agoAnd the rest of Marks (and others) buffalo https://gobuffalo.io/ https://gobuffalo.io/