Regarding recent discussion about null-safety in Go (https://news.ycombinator.com/item?id=38300425), here is a thread from Go forum in the pre-1.0 days where a user tries to highlight the problem and suggests a solution.
I think it is interesting because the user valiantly tries to argue his case but is repeatedly misunderstood (by a core dev, even) and in my view the proposal is not taken seriously. A little example of how small moments from history can have huge implications later on.
Choice quote: "It's a bit too soon to tell whether this will actually be a problem".
Comments
Regarding recent discussion about null-safety in Go (https://news.ycombinator.com/item?id=38300425), here is a thread from Go forum in the pre-1.0 days where a user tries to highlight the problem and suggests a solution.
I think it is interesting because the user valiantly tries to argue his case but is repeatedly misunderstood (by a core dev, even) and in my view the proposal is not taken seriously. A little example of how small moments from history can have huge implications later on.
Choice quote: "It's a bit too soon to tell whether this will actually be a problem".
That's the least generous interpretation/reply I've seen in a while.