I agree, writing Java without powerful refactoring tools is a bore--that's why it's great to use Eclipse's "Generate Getters and Setters based on Fields" refactoring tool.
Interestingly, I've never really felt the pain of not having a good REPL for java, although I often use it in other languages. Although Java isn't interpreted, unlike the other languages you mentioned, Scala is both interpreted and compiled, so it's not a great argument for why it doesn't have a good REPL. I think eclipse's very strong autocomplete somewhat obviates the need for it, because I know that I mostly depend upon bpython/ipython for the easy access to docstrings and information about arguments.
I wonder if part of the reason why I've never felt the need for a REPL in Java is simply because there isn't one built in, so it isn't a tool that I ever reach for. REPLs are great for prototyping, and for learning, but I've found that the more I learn about a language, the less I tend toward using the REPL, so perhaps it's simply that I got used to being able to edit my code instead of having to type it all in again.
Interestingly, I've never really felt the pain of not having a good REPL for java, although I often use it in other languages. Although Java isn't interpreted, unlike the other languages you mentioned, Scala is both interpreted and compiled, so it's not a great argument for why it doesn't have a good REPL. I think eclipse's very strong autocomplete somewhat obviates the need for it, because I know that I mostly depend upon bpython/ipython for the easy access to docstrings and information about arguments.
I wonder if part of the reason why I've never felt the need for a REPL in Java is simply because there isn't one built in, so it isn't a tool that I ever reach for. REPLs are great for prototyping, and for learning, but I've found that the more I learn about a language, the less I tend toward using the REPL, so perhaps it's simply that I got used to being able to edit my code instead of having to type it all in again.