I find it funny and sad that this is the sort of thing that people like to bring up as somehow bad and not the part where the Isrealites are admonished for not genociding the Cannanites hard enough.
Sort of, but the difference here is that it's really "blame the person who created the process, not the person following it". The people with the authority to alter faulty processes don't want to change it, even if it's clearly bad, because then they become "the person who created the process".
For what it's worth, it's more ceremony, but you can work fine with partially constructed data types without null, it's just that the nature of their construction either needs to encoded int the types directly, or they need to be initially constructed with defaults and you need to decide if you want them to explode/panic if they're not completed, or just return potentially unexpected defaults.
> The other thing I don't like is when you are experimenting and fleshing out an idea you want to take a try it and see approach but with Typescript you have to really commit even though you just want to experiment. When you want to change something there is so much more code that you have to change.
I've seen this opinion before, and I don't understand it in the slightest.
Let's say you're modeling a "user". You might initially think that users should have a first & last name, so you write it this way. Then later on you realize that there's no point in this distinction, and some of your users from Indonesia don't even have separate first & last names, so you want to switch to a single name.
* With weak/no typing, you have search around for anything that matches the field names, and hope to God you didn't miss anything.
* With stronger typing you just change it let the compiler tell you all the places you need to fix up.