4 ms·
On the other hand, Go does not have the benefit of the huge Java ecosystem.
by mercurial 14y ago
On the other hand, Go does not have the benefit of the huge Java ecosystem.
- kamaal 14y agoYou need the huge Java ecosystem and benefit from it only if you wish to be and use the Java ecosystem, which is basically a million different ways to use XMLs, abuse design patterns, needlessly make solutions verbose and complicated to make your work complex and very important. Other technologies will have their own ecosystem. Which will grow at their own pace as demand for that grows.
- mercurial 14y agoTrolling much? Of course you have a number of AbstractBeanXmlFactoryFactory, and it's generally pretty verbose, but you do have a large number of well-tested, well-performing solutions already established. And that's definitely an advantage when you have a problem to solve right now.
- lsh 14y agoAgreed - about Java and the trolling. All his comments on this topic is nothing but a troll.
- luriel 14y agoI count this as a Go feature.
- jlarocco 14y agoI don't think the Java ecosystem is really that great any more. There was definitely a time when it was the biggest and best, but I don't think that's been the case for a while. Is there anything in particular that's available in Java that you couldn't get in Go or Python?
- white_devil 14y agoIs there anything in particular that's available in Java that you couldn't get in Go or Python? A cross-platform UI toolkit that's pretty good all things considered? A reporting toolkit that produces PDFs according to custom templates? (Swing and JasperReports, respectively)
- mseebach 14y agoFirst of all, the number one component of the Java ecosystem is the JVM - a rock solid execution environment on pretty much any hardware/OS combination you're likely to find in the wild. Also, the JVM is a very decent environment. For one, it has no trouble with high levels of concurrency. Neither Python or Ruby particularly likes concurrence (but achieves it with multiple processes). Write once, run anywhere might have been a mirage when Java came out, it's not anymore. Next step on the ladder is languages. You can mix any combination of Java, Scala, Groovy, Clojure, JRuby, Jython and others with little or no friction. Then there's infrastructure. There's a good selection of rock solid application servers - Tomcat, Jetty and Glassfish comes to mind. The entire JDK toolchain, especially VisualVM, JConsole and JMX. Get a stacktrace or a heap dump from a running java process? Trivial and built in. Finally, the libraries: JDBC is pretty neat: Every database under the sun plugs into the same interface. Terracotta has a pretty interesting line up (http://terracotta.org/products http://terracotta.org/products). Hadoop - it's a full ecosystem of it's own. Eclipse and IntelliJ IDEA. Apache POI for MS Office doc manipulation. Apache FOP is supposed to be pretty powerful. Lucene. Apache Commons.
- espeed 14y agoGo is missing Java's NLP libraries.