It's actually neither: I haven't had any experience with the Java world, but Java programmers are generally a scorned class of programmers in my entire experience as a programmer. The concentration of beginner-level programming courses in university programs, and corresponding overabundance of entry-level Java programmers -- where 'entry-level' is a pretty generous term -- in the industry as a whole has led to a situation where "I'm a Java Programmer" in the age group I'm in is somewhat akin to "I'm a Visual Basic programmer", insofar as it typically relates more to knowing how to use a programming GUI to toss out things quickly with no concern for quality than it does to programming experience.
I've had a very very limited amount of direct exposure to Java, but the associations that programming Java tends to bring along are enough to act as an active discouragement to learning more about the toolchain. Combine this with relatively poor libre-free JVM support, and the verbosity of the language making the primary way of writing code GUI based (something that I've never been a fan of in my coding: I'm a command line/vim guy), and any interest I have in Java due to some Fancy New Announcement tends to go out the window pretty quickly once reality sets in.
I think that this is just a result of the environment I've typically worked in: Reading your entries has brought a significant level of respect for the Java World from the eyes of someone who is obviously a competent programmer. In general, if someone mentions Java without many other details, over something like say, Python, I have an expectation that the code will be either more basic or more complicated than (or both) a comparable alternative written in a different language. (C gets a 'more complicated and less basic' mark, on the other hand.) There is clear evidence in the posts you've made here that we have similar ideals for workflow of development of a project (even if not being my own boss means that I seldom actually get to follow up on them), despite what I would typically consider a chasm of difference in our toolset.
Hm, this has gone most everywhere. I think that it comes down to "Java has become the entry-level programming language: therefore, lots of programmers in Java only work at the entry-level, and I prefer to work in a different environment than people who work at the entry-level, and therefore my contact with Java has been limited." It's possible that I might like Java but my limited experience suggests that my nature is more Pythonic than... Javaic? Javaish? :)
(I can expand on any of the points if you're interested; I don't know what kind of environment you've typically worked in, so it's possible that this doesn't make any sense. I get the impression that you're older than I am by some number of years, which would probably mean that you were out of the 'entry level' arena long before Java became a defacto standard in it, for example.
no subject
I've had a very very limited amount of direct exposure to Java, but the associations that programming Java tends to bring along are enough to act as an active discouragement to learning more about the toolchain. Combine this with relatively poor libre-free JVM support, and the verbosity of the language making the primary way of writing code GUI based (something that I've never been a fan of in my coding: I'm a command line/vim guy), and any interest I have in Java due to some Fancy New Announcement tends to go out the window pretty quickly once reality sets in.
I think that this is just a result of the environment I've typically worked in: Reading your entries has brought a significant level of respect for the Java World from the eyes of someone who is obviously a competent programmer. In general, if someone mentions Java without many other details, over something like say, Python, I have an expectation that the code will be either more basic or more complicated than (or both) a comparable alternative written in a different language. (C gets a 'more complicated and less basic' mark, on the other hand.) There is clear evidence in the posts you've made here that we have similar ideals for workflow of development of a project (even if not being my own boss means that I seldom actually get to follow up on them), despite what I would typically consider a chasm of difference in our toolset.
Hm, this has gone most everywhere. I think that it comes down to "Java has become the entry-level programming language: therefore, lots of programmers in Java only work at the entry-level, and I prefer to work in a different environment than people who work at the entry-level, and therefore my contact with Java has been limited." It's possible that I might like Java but my limited experience suggests that my nature is more Pythonic than... Javaic? Javaish? :)
(I can expand on any of the points if you're interested; I don't know what kind of environment you've typically worked in, so it's possible that this doesn't make any sense. I get the impression that you're older than I am by some number of years, which would probably mean that you were out of the 'entry level' arena long before Java became a defacto standard in it, for example.