Java is confusing, Clojure is simple
blog.klipse.tech
Java is confusing, Clojure is simple
1–10 of 25 posts
Re: Java is confusing, Clojure is simple
#2The article focused on confusion among students learning the language.
First, imperative programming is important to learn. Understanding the stack/heap and calling conventions is important. Yes, those things are hard to learn. But once you learn them, they are not that confusing. These are significant pedagogical concerns, but I'm not sure they are so important beyond the classroom.
Second, FP is also confusing to new programmers but for different reasons. E.g. anything that requires folds is typically easier in imperative settings.
Re: Java is confusing, Clojure is simple
#3The article focused on confusion among students learning the language. First, imperative programming is important to learn. Understanding the stack/heap and calling conventions is important. Yes, those things are hard to learn. But once you learn them, they are not that confusing. These are significant pedagogical concerns, but I'm not sure they are so important beyond the classroom. Second, FP is also confusing to n…
Why imperative programming is important to learn? What will we be missing in a LISP only world?
Re: Java is confusing, Clojure is simple
#4The article focused on confusion among students learning the language. First, imperative programming is important to learn. Understanding the stack/heap and calling conventions is important. Yes, those things are hard to learn. But once you learn them, they are not that confusing. These are significant pedagogical concerns, but I'm not sure they are so important beyond the classroom. Second, FP is also confusing to n…
Why imperative programming is important to learn? What will we be missing in a LISP only world?
understanding performance characteristics ( memory consumption in particular ) better ?
Re: Java is confusing, Clojure is simple
#5The article focused on confusion among students learning the language. First, imperative programming is important to learn. Understanding the stack/heap and calling conventions is important. Yes, those things are hard to learn. But once you learn them, they are not that confusing. These are significant pedagogical concerns, but I'm not sure they are so important beyond the classroom. Second, FP is also confusing to n…
I agree that imperative programming is important to learn but java is in my opinion shouldn't be the language to do so. I think learning should be fun and java is the exact opposite of fun. It's wordy, full of boilerplate and enterprise code. Java, in contrast to other major languages, doesn't have an inspiring narative or a reason to be.
Re: Java is confusing, Clojure is simple
#6The article focused on confusion among students learning the language. First, imperative programming is important to learn. Understanding the stack/heap and calling conventions is important. Yes, those things are hard to learn. But once you learn them, they are not that confusing. These are significant pedagogical concerns, but I'm not sure they are so important beyond the classroom. Second, FP is also confusing to n…
Why imperative programming is important to learn? What will we be missing in a LISP only world?
Nulls, dumb syntax, bugs, my high blood pressure...
In 2013 I tried darn hard to get a job doing Clojure but it never panned out. The world just isn't ready, it seems.
Re: Java is confusing, Clojure is simple
#7The author forgot to mention that you can have immutable collections in Java but then praises Clojure's immutable collections. The Java coded provided will produce warnings due to the mixing of generics and raw types and actually I had no idea about what the output of the Clojure code would be because the author assumes that you have no questions "once a Clojure learner gets used to Clojure syntax". Once you learn that there's a difference between primitives and objects then the Java example becomes just as clear. Moot article.
Re: Java is confusing, Clojure is simple
#8The article focused on confusion among students learning the language. First, imperative programming is important to learn. Understanding the stack/heap and calling conventions is important. Yes, those things are hard to learn. But once you learn them, they are not that confusing. These are significant pedagogical concerns, but I'm not sure they are so important beyond the classroom. Second, FP is also confusing to n…
Why imperative programming is important to learn? What will we be missing in a LISP only world?
LISP is imperative.
Re: Java is confusing, Clojure is simple
#9The article focused on confusion among students learning the language. First, imperative programming is important to learn. Understanding the stack/heap and calling conventions is important. Yes, those things are hard to learn. But once you learn them, they are not that confusing. These are significant pedagogical concerns, but I'm not sure they are so important beyond the classroom. Second, FP is also confusing to n…
I agree that imperative programming is important to learn but java is in my opinion shouldn't be the language to do so. I think learning should be fun and java is the exact opposite of fun. It's wordy, full of boilerplate and enterprise code. Java, in contrast to other major languages, doesn't have an inspiring narative or a reason to be.
Having recently taken a few courses in Java, learning things like data structures can be fun, but it depends a lot on the instructor and the exercises provided.
Re: Java is confusing, Clojure is simple
#10This feels like someone who prefers Clojure really hard, and doesn't like Java.
Admittedly, I'm a finance Java EE wageslave, but java is really not that complex to understand. Objects are references, updating the referenced object will change all objects sharing that reference.
Primitives are an admittedly confusing bit, but we're kinda stuck with them.
I don't think Java is "confusing" (but I am a bit biased), but deliberately avoiding understanding the language isn't the same as confusing.