this post was submitted on 16 Jul 2025
77 points (93.3% liked)
Programming
24010 readers
445 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities
!webdev@programming.dev
founded 2 years ago
MODERATORS
I get your point, but that's not a great example. Kotlin is a statically typed language, and this compiles (and runs!) just fine:
Even
val test: String = 1 as Stringwill compile, but at least gives you an exception at runtime, which the equivalent typescript wouldn't.That's crazy, I thought that would be an invalid cast or something.
Unfortunately not. You do get a warning that it's an unchecked cast at least.
Granted, the issue here is generic type erasure, which was a tradeoff that was decided on for backwards compatibility when generics were first introduced to Java, so it's not like an actually desirable feature of the language. But the point is that this wouldn't be reason for anyone to not call Java and Kotlin not statically typed, their type system is just a bit weaker than others in certain aspects