2 ms·
I really appreciate that people are thinking about language ergonomics in a serious way. I've recently been using Flutter and it's a delight to get an error me
by wpietri 7y ago
I really appreciate that people are thinking about language ergonomics in a serious way.
I've recently been using Flutter and it's a delight to get an error message like "you did X, but Y was uninitialized, so you need to put a call to Y.Z in your code first". When my problem is some conceptual mistake, a traditional error message, like "null pointer error in Y" just confuses me, because I don't even know what Y relates to what I'm doing.
I love that you and others are taking the time to see what really went wrong. Partly because it solves my immediate problem, but also because I know that's exerting backpressure on confusing language and library features, which I hope will drive more platform improvements down the road.