Discussion

Sign in or Join to comment or subscribe

2022-04-13T04:50:59Z ago

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 Santo

Jerod Santo

Bennington, Nebraska

Jerod co-hosts The Changelog, crashes JS Party & takes out the trash (his old code) once in awhile.

2022-04-13T14:07:36Z ago

Thanks for commenting! A few responses:

If you donā€™t like dealing with SQL to interact with databases then ActiveRecord seems like an ideal tool for you.

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 am surprised nobody mentioned pipes in the ā€œmissing featuresā€ section.

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.

I predict go will change error handling by the time 2.0 rolls around.

Two bold predictions! 1) The errors thing, and 2) that Go 2.0 will roll around. šŸ˜‰

2022-04-22T19:03:51Z ago

In the podcast it was discussed that if you have many

if err != nil {
  return err
}

Itā€™s an anti-pattern and there are ways to avoid it.

Please comment here on your suggestions for solutions to this problem

Player art
  0:00 / 0:00