The ooooooone point I might argue is zero-dep. I build go for scratch base images all the time. Scratch is literally zero bytes, and only provides /.
/
As for learning curve... Yes. It's a bit of a beast lol. gofmt helps a lot - intellij, with its auto gofmt helps more.
gofmt
Dealing with json - especially uncertain json - is... I don't talk about that.
For me, the draw was true cross-compile, and it's sheer perf. If you need quicker than Go, you need C.
I don't need C 😂
😂 and I have met folks who thinks my alpine approach is "hardcore" haha.
And yes I so want go to have a better way to handle uncertain json data.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The ooooooone point I might argue is zero-dep. I build go for scratch base images all the time. Scratch is literally zero bytes, and only provides
/.As for learning curve... Yes. It's a bit of a beast lol.
gofmthelps a lot - intellij, with its autogofmthelps more.Dealing with json - especially uncertain json - is... I don't talk about that.
For me, the draw was true cross-compile, and it's sheer perf. If you need quicker than Go, you need C.
I don't need C 😂
😂 and I have met folks who thinks my alpine approach is "hardcore" haha.
And yes I so want go to have a better way to handle uncertain json data.