Hacker News Reader

For every type of projects I'm involved, I choose Go as the backend and put maximum of business rules there to help me manage changes. Go standard library is sufficient and robust for many (all) cases I faced : http handlers, templates, concurrency...

If a web frontend is needed, I'll take svelte (not svelte kit) to code independente components that talk to the backend. I'll code there only interface logic (no control, no calculation, etc...)

View on HN

I made a few apps in Go with mostly just standard library (I used the Chi router). The first API was fun but I never felt as productive as I did with Django.

If I do a Go project now I usually try to push the team to consider more libraries and frameworks to take care of the repetitive tasks.

It's just that Go and their libraries are never going to be as expressive as something like Python and Django. I really appreciate the language for its simplicity, I love getting a single binary, the ecosystem is nice and it's great to be able to read the stdlib code and code from other libraries easily. However, if I have to be frank, I'm much more productive and have a better time with something like Django.

Reply on news.ycombinator.com