5 ms·
Having introduced Golang in a business environment in 2014 and having seen the language solve real problems at that time, at scale, I feel that if your own reas
by sebcat 8y ago
Having introduced Golang in a business environment in 2014 and having seen the language solve real problems at that time, at scale, I feel that if your own reason to not use Go is GOPATH... Either Go does not solve any real problems for your use case, or your reasons to use Go is misaligned.
GOPATH is really not a problem, but efficient concurrency is. Go made the company I worked for go from 20 deployments for a service to 1 (I/O bound), reducing the costs for that service a lot. If you are willing to let the environment get in between that...
Of course, you could have implemented that system using assembler for all I care, but Go really made it possible within that organization, something Java, C and other languages failed at before Go was introduced.
N=1, ymmv, &c
- apta 8y ago> something Java, C and other languages failed at before Go was introduced. Java's concurrency solutions are just as good, if not better than golang's. Pair that with libraries such as RxJava and you're definitely ahead. I don't see what golang has to offer in that area that the JVM doesn't
- sebcat 8y agoSounds believable, but at the time we were stuck at 1.6 and had a significant drop in traffic due to JSSE and non-existing support of "modern" TLS Cipher Suites and TLS extensions (we even had problems with SNI, years after introduction)... We were using C because epoll made it possible for us to compete, but the Java reactivex stuff were lagging behind.
- apta 8y agoMoving to a completely different language and platform was easier than moving from Java 6 to Java 8? Why were you stuck on 6 otherwise?
- dagenix 8y agoGo may very well have been through best fit for you. However, saying that Java's problem was that you couldn't upgrade from 1.6 yo 1.8 but you could introduce a completely different language doesn't make much sense to me.
- _-david-_ 8y agoWhy couldn't you have just put a reverse proxy in front of your java?
- cweagans 8y agoYou don't have to deal with the jvm for one thing. Java for another. Both of those things are selling points for me.
- baby 8y agoBut then you have to write java
- paxy 8y agoThe problem was never GOPATH itself, but the fact that the restriction made it impossible to manage versions and dependencies in a sane way.