4 ms·
And it's terrible because there's both `null` and `undefined` which have largely the same meaning but aren't equal. Depending on what you're interacting with,
by gnabgib 4y ago
And it's terrible because there's both `null` and `undefined` which have largely the same meaning but aren't equal. Depending on what you're interacting with, you may need to use one over the other or coerce. Especially common with developers from other languages who don't even know of the gotcha
- 8note 4y agoI've never found a use for null where undefined wouldn't be simpler to use. Especially with the ?? Operator to set defaults along the way
- j1elo 4y agoThis is a very curious and fun way to put it: https://stackoverflow.com/a/57249968 https://stackoverflow.com/a/57249968 In essence, `undefined` is non-existence. And `null` is existence with a non- (or "invalid", or "unknown") value. Although using them like that depends on the needs of the application. If "invalid" or "unknown" was an expected user choice, I would still rather encode it as an enum better than a nullable boolean, as mentioned in my comment above.