3 ms·
All the weird cruft around nullability, for starters. Once again confirming that allowing null references is usually a mistake.
by munchler 5mo ago
All the weird cruft around nullability, for starters. Once again confirming that allowing null references is usually a mistake.
- dgellow 5mo agoDo you mean the implicit nullable types? Now that you can make nullable explicit instead I really don’t have much issues with it. It is part of the type system, as it should, and you have null coalescing operators. Is it still problematic or are you dealing with older codebases where you cannot set the nullable pragma?
- munchler 5mo agoYes, all that stuff. I try to stick to F# where no special syntax is required for missing values (via Option<T>).
- setr 5mo agoGiven that they already made the billion dollar mistake, I find their handling for nulls the best possible thing they could do at this point. I’d hardly call it crazy — rather, it’s exceedingly pragmatic.
- vips7L 5mo agoPersonally I prefer T? over Option[T]. Monads just add extra typing and destructuring for no reason. It’s definitely the pragmatic choice.