> First, you suggest that Java is only hanging on due to lock-in and > that it lacks genuine developer interest. You could similarly say that > developers use the HTTP protocol because of "lock-in" rather than > being genuinely passionate about the protocol itself.
You're confusing standards with tools. > Developers > aren't passionate about the specifics of Java's language syntax. But > they are passionate about cloud computing, big data, advanced parallel > computing paradigms, alternative programming languages, NLP, data > mining, machine learning, and tons of other areas that have very > vibrant and passionate communities where the Java ecosystem and tech > stack plays a prominent role. Of course it does. When have I said it doesn't? > You don't think there are large, complex, and successful scientific > and server side web apps built in Java? Even on the client, you have > things like Minecraft and Android. Sure I do, again when have I said otherwise? But large general purpose end-user applications are rare at best. Android can not be used as an argument here, it is legally and technically not Java (JSE, JME or JEE) as it's a completely different VM and runtime environment. And even on Android, you have to resort to C and Renderscript to do push the performance envelope. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
