← Back to context

Comment by flanked-evergl

14 hours ago

No amount of proven points will give Go null safety, though.

Yet the whole Docker, Kubernetes, CNCF ecosystem is powered by Go, doesn't seem to have been hindered by lack of null safety.

Same applies to GCP, AWS and Azure, powered mostly by Java, C# and C++.

People should stop being so obsessed with one specific language feature, when there is so much C and C++ code being produced every day.

  • And Linux kernel is written in C etc, so by this logic you don't even need memory safety. There is no good excuse for designing a language in modern times (this century) with every object nullable by default. C# at least mostly has solved this design mistake later by introducing nullable reference types (https://learn.microsoft.com/en-us/dotnet/csharp/nullable-ref...). Then again, Go designers insisted that generics were also unnecessary, until they changed their mind.