Re:Ask HN: Programmers who don't use autocomplete/LSP, how d...
by dismalaf on Tuesday December 24, 2024 @05:49PM
(#42505511)
Of course it's Python people who come up with this nonsense...
Re:Ask HN: Programmers who don't use autocomplete/LSP, how d...
by IshKebab on Wednesday December 25, 2024 @03:30AM
(#42507688)
Do you have a better name suggestion?
Re:Ask HN: Programmers who don't use autocomplete/LSP, how d...
by Izkata on Wednesday December 25, 2024 @09:33AM
(#42508952)
They said it in their first comment: dynamic typing
Re:Ask HN: Programmers who don't use autocomplete/LSP, how d...
by IshKebab on Wednesday December 25, 2024 @02:06PM
(#42510489)
Not a good option - then you'll get a whole different set of pedants saying that Python is always dynamically typed, which I think is a lot more reasonable than quibbling over the use of "untyped" to describe Forth.
Re:Ask HN: Programmers who don't use autocomplete/LSP, how d...
by dismalaf on Thursday December 26, 2024 @01:07AM
(#42513451)
Adding type annotations doesn't make Python statically typed. Type annotations are borderline meaningless, they're basically just a type of documentation that helps your tools spit out better suggestions and makes your tools yell at junior developers.
Python isn't taking advantage of type annotations to produce better compiled code or anything, it's still a dynamic language that infers types at runtime.
Re:Ask HN: Programmers who don't use autocomplete/LSP, how d...
by IshKebab on Thursday December 26, 2024 @04:03AM
(#42514027)
Yeah that's exactly what I was saying. So what word would you use to mean "dynamically typed without static type annotations"?
> your tools yell at junior developers.
Oh you're one of those...
Re:Ask HN: Programmers who don't use autocomplete/LSP, how d...
by dismalaf on Thursday December 26, 2024 @07:40PM
(#42519035)
> one of those...
If by one of those you mean a solopreneur who doesn't have any junior devs to yell at then yes. If I wanted to use static types I'd use an actual statically typed language with all of the performance benefits (Go, Java, Rust, Haskell, Ocaml, etc...).
Using a dynamically typed/interpreted language with type annotations is literally the worst of all worlds...
Well, now you have! Here are some examples:
https://0xda.de/blog/2024/03/untyped-python-sucks/
https://lucumr.pocoo.org/2023/12/1/the-python-that-was/
In fairness I think it is a fairly recent linguistic shift, probably because there's no debate between weakly typed and strongly typed - strongly typed is oblivious the right answer. Instead the debate is between dynamically-typed-without-static-type-annotations and statically-typed-or-dynamically-typed-with-static-type-annotations, but obviously people need a more succinct term for that.
> Like, no one would call Ocaml untyped if you used type inference and didn't spell them out yourself... Or if you used the auto keyword everywhere in C++... The Ruby and Python runtimes both definitely enforce types.
Static type inference still counts as having static types. That's totally different to dynamic typing without static type annotations ("untyped").