4 ms·
Been there, done that. I don't agree. Go's native html/template and even pongo2 or quicktemplate etc have a big problem when it comes to conditional fragments o
by lakomen 3y ago
Been there, done that.
I don't agree.
Go's native html/template and even pongo2 or quicktemplate etc have a big problem when it comes to conditional fragments of some text.
It's messy and you end up writing helper functions for pretty much everything.
Need a href aware navbar?
Custom function and macro time.
Bleh.
Performance is great, maintainability isn't.
I dislike graphql because it's too mich overhead.
RESTful is not good enough, only good for admin UI CRUD.
I moved to json rpc calls.
So I can have the best of both worlds.
However what I'd really like to have is a proper SSR component framework that is interactive or rather reactive.
- granshaw 3y agoJust use Rails
- cpursley 3y agoThese days it’s hard to justify Rails over Phoenix for fresh projects.
- granshaw 3y agoFine then, Phoenix :) But yeah Go is not a good ecosystem for comprehensive web development
- lakomen 3y agoWith Rails you're back in the low performance camp sadly, might as well go full JS. I want my cake and eat it too. For Go, unless I missed some new development, there's Kyoto and jfyne/live . And that's it for Go. Kyoto IMHO is more of a poc. And live is not very appealing, you're back in complicated camp with it.