Why GoLang supports null references if they are billion dollar mistake?

This page summarizes the projects mentioned and recommended in the original post on reddit.com/r/golang

Our great sponsors
  • Zigi - Workflow assistant built for devs & their teams
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • SonarQube - Static code analysis for 29 languages.
  • Scout APM - Truly a developer’s best friend
  • Optional

    A robust option type for C#

    Not really. C# doesn't have monads but you can easily add something like https://github.com/nlkl/Optional which is great for a team familiar with option types and IMO will lead to a more productive team with a more concise code base.

  • goderive

    Derives and generates mundane golang functions that you do not want to maintain yourself

    Now, am I going to do the same with a library like goderive just so I can use FP techniques to get, amongst some other things, less nil checks? No. Probably not. If I wanted to use primarily FP techniques in my code, I would probably be using something else in the first place. Go isn't a great environment for guaranteeing immutability for starters, so anything like that is necessarily going to be an incomplete experience. And in the bargain, my code would, in my opinion at least, be less readable and maintainable.

  • Zigi

    Workflow assistant built for devs & their teams. Automate the mundane part of your day, with live actionable messages for your GitHub & Jira tasks.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts