Strong typing, a hill I'm willing to die on

Re:Strong typing, a hill I'm willing to die on by leptons on Wednesday October 04, 2023 @01:49PM (#37768953)

I also hate autocomplete. It just gets in my way. Autocomplete doesn't really work unless you already know what you're going to code, and if you already know what you're going to write the autocomplete prompt just gets in the way and often messes with keyboard entry of what I was typing. I just switch it off, it never saved me any time and just gets kind of annoying.

[ Parent | on HN ]

Re:Strong typing, a hill I'm willing to die on by spankalee on Wednesday October 04, 2023 @02:53PM (#37769881)

> Autocomplete doesn't really work unless you already know what you're going to code

Say what? Autocomplete is a godsend for quickly working with new APIs. If you're writing a function that takes some objects that you're not familiar with autocomplete can pretty quickly lead you down a good path.

[ Parent | on HN ]

Re:Strong typing, a hill I'm willing to die on by leptons on Wednesday October 04, 2023 @06:25PM (#37772642)

That's not my experience. If I'm working with new APIs, I have the docs up on one screen and the code on the other, and I've probably already copied and pasted the function and parameters into my code from the docs before autocomplete can get in my way. You do read the docs, don't you?

[ Parent | on HN ]

Re:Strong typing, a hill I'm willing to die on by spankalee on Wednesday October 04, 2023 @08:00PM (#37773325)

Sometimes I read docs. Other times autocomplete (and hover-over docs) gives me exactly what I need right when and where I'm actually writing code.

Static typing makes it easier for my computer to get me the relevant docs.

[ Parent | on HN ]

Re:Strong typing, a hill I'm willing to die on by cellularmitosis on Thursday October 05, 2023 @11:56AM (#37780254)

I cant even imagine trying to use the iOS SDK without autocomplete.

[ Parent | on HN ]