> You can use an IDE that displays inferred types as type inlays
This isn't captured in the code & that is a huge weakness. Being able to see the code change over time is, in my view, a huge advantage.
Reliance on high-tech tools to discern meaning & do the inference for us feels far weaker than simply encoding the good information into the code. That just seems far better to me, far more robust. Some of this is that I'm a vim user and don't want to have to go lookup & configure a LSP daemon for each file I evaluate, but some of it just feels like base common sense, that the tradeoff of actually being explicit are overwhelming & clear.
I think I argued against this pretty resolutely the first time around. I don't think your post adds anything or changes my mind at all.
This isn't captured in the code & that is a huge weakness. Being able to see the code change over time is, in my view, a huge advantage.
Reliance on high-tech tools to discern meaning & do the inference for us feels far weaker than simply encoding the good information into the code. That just seems far better to me, far more robust. Some of this is that I'm a vim user and don't want to have to go lookup & configure a LSP daemon for each file I evaluate, but some of it just feels like base common sense, that the tradeoff of actually being explicit are overwhelming & clear.
I think I argued against this pretty resolutely the first time around. I don't think your post adds anything or changes my mind at all.