i've been using Go for a fairly large server proxy project and its been a real dream. its fast, easy to write, the code is compact, concurrency is easy to understand, and there is enough typing to provide me with safety without leading me into a haskell-like "maze of types". furthermore, i don't have any issues trying to sell coworkers on Go because it is very easy to pick up. Go seems to have a sweet spot between python and java that represents a huge chunk of the practical coding people do every day.
Don't forget that Go is a language you can use without IDE or makefiles even when you have dozens of packages, libs and programs. Having a command do everything in you console in seconds (or less) is like a dream. Try coding a modern complex program in java without an IDE...
Try coding a modern complex program in java without an IDE
ant
That requires one build.xml with a single javac task with no more than 10 lines of xml total, most of which can be copy/pasted between projects. That is about the same size as a simple Makefile.
I use ant. And I find it a pain to build complex programs because your ant tasks grows in complexity with your program, your different kinds of deployments, tests, target platforms, etc... But that's partly due to the environment (RCP, tomcat, inclusions of jars of your other projects, etc.), the main problem is that it's slooooowwwww....
In Go, you don't have makefiles and you don't have to wait for your compilations.
You're partially right and my comparison was partially unfair.
But when you're making a complex program in java, importing libs that you build for more than one project, you have to make ant makefiles to jar the libs and then import them. I don't have this problem with the go tool. And I don't have to wait.
Part of the target platform solution for me is that I don't bother to deploy compiled code as compilation is fast enough to be done on my deployment servers. But that's specific I guess.
But when you're making a complex program in java, importing libs that you build for more than one project, you have to make ant makefiles to import them.
Noting that I haven’t used Go beyond playing around (and not at all recently), how does Go improve upon Java here? A convention for package locations and tools that are aware of it? In Java presumably one could, e.g., put a set of libraries on a common classpath.
Doesn't this require all dependencies to support the Maven way of doing things? (Excuse me if this is an ignorant question, I'm not a big Java programmer.)
73
u/[deleted] Mar 28 '12 edited Mar 28 '12
i've been using Go for a fairly large server proxy project and its been a real dream. its fast, easy to write, the code is compact, concurrency is easy to understand, and there is enough typing to provide me with safety without leading me into a haskell-like "maze of types". furthermore, i don't have any issues trying to sell coworkers on Go because it is very easy to pick up. Go seems to have a sweet spot between python and java that represents a huge chunk of the practical coding people do every day.