import (
"net/http"
"github.com/labstack/echo"
)
But you still need jre/jdk to serve HDFS ;) Also, there are tons of other missing products like ElasticSearch, Kafka, Spark...
Sure, but fight the battles you can win. The database I use wasn't written in C. That doesn't mean I have to write applications in C.
*was written in C
Yeah, I don't doubt that there are many more Java libs. But for most uses cases today there are Golang libs as well. There's a Kafka client by Confluent, Elasticsearch client etc.
We used the same argument a decade ago with Perl, look where that got us.
Java in 2018 is Perl in 2008, roughly.
Re:Oracle’s Java 11 trap
by StreamBright on Wednesday September 26, 2018 @10:48AM
(#18076479)
Actually I never used this argument for Perl. Perl was not really used for things like big data or high performance backend applications. You can use this reasoning for C++ or C# on the other hand and it stands. Many "big data" things re in C++ and a lot of high performance projects out there.
If you want to compare nifty scripting languages than you can compare Perl with Ruby or Python. In 2008 I was happily using Ruby for most of things we used to do in Perl, a bit slower yes, but who cared and it was much more readable.
import org.apache.hadoop.*;
import org.rapidoid.net.Server;
In case you are wondering people not only using languages for language features but also for the quality/quantity of libraries available in those languages. This is why is very hard to bootstrap a new language. Java has a ton of great libraries that are essential to big data and high performance backend services that you do not have in Go. I could mention tooling as well but we can skip it for now, the aforementioned library situation is enough to not to consider go already. Btw. the new OpenJDK releases are just fine for running Java and many companies use it extensively already (like AWS EMR for example) to run production code.