Ruby has Modules, but many, many common libraries do not use them. I had fun recently debugging a project that (through transitive dependencies) relied on two different "progress bar" libraries, both with a class called "Progress", and neither of which was namespaced. Namespaces solve a real problem.
Of course, that can be solved with proper tooling, but some people are just averse to using something more heavyweight than necessary.
- make things unique
- group things logically (which makes the systems design more explicit)
This applies to all programming languages. It's just that there's a convention in the Java community to prefix namespaces with a FQDN, which adds to the length. But you're free to choose another convention if you fancy. Although I wouldn't recommend since it's not a major issue, especially considering IDE support.
Writing Java is unbearable without Eclipse/Netbeans. .NET a little bit less unbearable
If your IDE "works harder" than your compiler, something seems wrong to me (of course we all expect things like syntax highlighting today)
(Also I have written a fair amount of Java in vim and I didn't find it any more frustrating than writing Ruby in vim. And I don't even like Java.)
Probably doing socket programming in C is easier than in Java
(to be fair, it wasn't Java really, it was "OO evangelists" most likely, starting with C++ then going crazy with Java. Too bad they didn't even touch smalltalk
Actually... networked programming is really easy in Java.
You are right though the state of a lot of java libs is hilarious! Smalltalk seems really cool but I've never had a reason to devote time to it.
I learned OOP with Smalltalk/V, wrote some apps with Actor on Windows and, when first confronted with C++ I closed the book in horror and only came back 8 years later.
And even without an IDE, it's hardly that difficult to use namespaces. As has been mentioned here already, they solve a real problem, are necessary, and are much better than not having them.
This just seems like ignorant hating.
It's hard for a Java zealot to understand this position for some reason.
It's just a way to run code interactively. "A whole REPL" is something that usually fits in 10 lines of code. With comments.
I don't hate Java. In fact, along with Python and C, it's one of my favorite (and more used) languages. But I do realize it has a huge potential for being abused in horrible ways.
Don't blame the language for what some guys do with them.
The only reason you see the fully qualified class names is because the IDE does this automatically for you. If there were no IDEs everyone would be using the *s;
On the flip side, wildcard imports make coding much more fluid and concise. How many times have you had to hit ctrl+space two or more times in the same declaration to add import statements for interfaces and classes from the same package? IMHO, explicit imports greatly decrease the usefulness of the static import feature.
Pretty much everyone uses an IDE anyway so it's not like namespaces are ever an issue unless you do come across that rare name clash.
This 'its good enough, and everyone does it anyway' attitude leads us to incredibly damaging status quos.
import edu.syr.pcpratts.rootbeer.testcases.rootbeertest.serialization.MMult;
This seems like a pretty amazing project if the claims are true, though - I wasn't aware that CUDA was able to express so many of the concepts used to implement Java applications. The performance data in the slides is certainly compelling!