Answering questions for the Go-curious
Has Go caught your interest, but you just haven’t had the time/opportunity to really dig into it? Are you relatively productive in your current language/ecosystem but wonder if the grass truly is greener on Go’s side of the fence? If so, this episode’s for you!
Sign in or Join to comment or subscribe
A few comments on this episode.
If you don’t like dealing with SQL to interact with databases then ActiveRecord seems like an ideal tool for you.
Mnesia provides a distributed data storage solution that integrates with the language (erlang and elixir).
I am surprised nobody mentioned pipes in the “missing features” section.
Go does not force you to handle errors. You can ignore them completely if you want, you don’t even have to pass them up the chain. Java at least has checked exceptions. I predict go will change error handling by the time 2.0 rolls around.
Jerod co-hosts The Changelog, crashes JS Party, and takes out the trash (his old code) once in awhile.
Thanks for commenting! A few responses:
If this is in response to Kris’ cry for new ways of talking to databases… I’m pretty sure he’s unimpressed by today’s set of ORMs.
I didn’t want to pile on since the original question was for those using Go on the regular. But yeah, I miss pipes wherever I am that they are not.
Two bold predictions! 1) The errors thing, and 2) that Go 2.0 will roll around. 😉
In the podcast it was discussed that if you have many
It’s an anti-pattern and there are ways to avoid it.
Please comment here on your suggestions for solutions to this problem