Dynamic typing is not a "bad habit". I'm personally a fan of static typing, and write a lot of Rust, but dynamic typing is a valid engineering decision, especially for beginners.
This isn't an argument I'm interested in having with you. I could just as easily say, "why is it acceptable to have null values? Is discovering a bug at runtime better than at compile time? My favourite language, Rust, does not have nulls."
But that would be off topic and pedantic because we're discussing something completely other.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I recommend Python only as an example; but I think Java is too large a language to teach as a first language.
Regarding the Java compiler used, obviously Eclipse uses the JDT incremental compiler - but I doubt any student is taught that in their first class!
Teaching Java doesn't mean to teach every aspects of it, you can do a lot with a subset of Java.
Python being dynamically typed, isn't it confusing (or magic) for students and a source of bad habits?
Dynamic typing is not a "bad habit". I'm personally a fan of static typing, and write a lot of Rust, but dynamic typing is a valid engineering decision, especially for beginners.
"dynamic typing is a valid engineering decision"
Why?
Is discovering bug at runtime better than at compile time?
Strange view of what software engineering is.
This isn't an argument I'm interested in having with you. I could just as easily say, "why is it acceptable to have null values? Is discovering a bug at runtime better than at compile time? My favourite language, Rust, does not have nulls."
But that would be off topic and pedantic because we're discussing something completely other.