3 ms·
I know a case (second hand) where they migrated from a Java backend to Go, then had to roll it all back to Java because it was too hard and error prone to maint
by the_af 6y ago
I know a case (second hand) where they migrated from a Java backend to Go, then had to roll it all back to Java because it was too hard and error prone to maintain. This is a very successful business, not a startup. No idea why they felt they had to migrate to Go in the first place.
I'd rather not mention the company, even though I did not work there.
- thebean11 6y agoYeesh, I can't imagine migrating a large backend codebase from any language to any language. And we're talking about migrating from Java..which is extremely well supported and probably the easiest language to hire for..
- nine_k 6y agoConcurrency is something that Go makes much easier, or at least more ergonomic, that Java with Runnables and ExecutorPools.
- Groxx 6y agoIt makes it easier to start concurrent stuff, but without ready-to-use type-safe abstractions like Java provides I'd say it's far harder to make correct concurrent stuff in Go. And while the race detector is wonderful, especially since it's baked in, it's nowhere near sufficient.
- apta 6y agoI disagree. There is so much boilerplate involved with managing concurrency in golang compared to Java. It's very error prone in practice and difficult to extend and manage. golang has nothing remotely close to `java.util.concurrent`.
- kjksf 6y agoAnd as a counterpoint there are many non-hearsay examples where teams migrated large projects from C++/Java/Python/Ruby/JavaScript to Go. Described publicly like Dropbox's backend migration to Go: https://twitter.com/jamwt/status/629727590782099456 https://twitter.com/jamwt/status/629727590782099456 I could give you tens examples of that, many have been posted on HN.
- the_af 6y agoNo need to counterpoint my example. The original list of case studies already lists Go's success stories. I was just providing the example the parent post was asking about. And note it's "hearsay" to you only because I didn't name the company and people involved -- because I was told this in confidence -- but this is a major company where I'm from, and their attempt at adopting Go ended up in disaster. Just a data point, that's all.