3 ms·
You've obviously been burned by null pointers (probably not just once). And you think they are a problem, and you're right. And you think they are a mistake,
by AnimalMuppet 4y ago
You've obviously been burned by null pointers (probably not just once). And you think they are a problem, and you're right. And you think they are a mistake, and you could be right about that, too.
But they're not the only problem. Writing async network servers can be a problem, too. Go helps a lot with that problem. If for your situation it helps more with that than it hurts with nulls, then it can be a rational choice.
And, don't assume that go must be a bad choice for all programmers, in all situations. It's not.
- bb88 4y agoAnd it's certainly not perfect in writing async network servers. It adds new concurrency bug types: https://songlh.github.io/paper/go-study.pdf https://songlh.github.io/paper/go-study.pdf
- lmm 4y ago> But they're not the only problem. No, but they're literally more than 50% of bugs, in my experience, so they're a bigger problem than all your other problems put together.