2 ms·
I agree with pretty much everything you said except this one: > In general I like how Go feels like it’s a Unix tool, where Java always felt like they were try
by littlestymaar 6y ago
I agree with pretty much everything you said except this one:
> In general I like how Go feels like it’s a Unix tool, where Java always felt like they were trying to rewrite the world.
Go is pretty much on par with Java when it comes to rewriting the world albeit not in the same way: they have their own assembly, their own linker, and even have their own libc using raw syscall (even doing so on windows and Mac for a while, which caused issues because there is no syscall stability there). And since it has a poor FFI, many Go developers end up rewriting their own libs in Go for pretty much everything when they need one lib.
- doctor_eval 6y agoYeah - I agree, and I suppose given the history and people who wrote Go, I tend to give it a pass here where maybe I shouldn’t. I also don’t tend to do any work in C any more so haven’t noticed that. I would say though that Go library calls work more like Unix/stdlib calls than Java, which makes abstractions out of even the most basic stuff, like filenames. But my point was more that, relative to Java, the performance and CLI tools feel very Unix like, they remind me of my C programming days. I mean Javac/mvn/gradle are all so slow relative to Go; Java command line tools don’t really seem to care about developer ergonomics. It’s hard to imagine chaining a bunch of Java CLI tools together with pipes! This is more because of the long startup times and cost of the JVM, but that too is part of the problem.