4 ms·
That's a trend I witnessed first hand while working as dev for a bank. Old Java code slowly being phased out for Go. Which to me seemed like madness at the time
by hu3 7y ago
That's a trend I witnessed first hand while working as dev for a bank. Old Java code slowly being phased out for Go. Which to me seemed like madness at the time due to lack of generics but it turned out to be fine, just needed a different mindset. This often resulted in a much shorter edit-compile-run loop and halved the hardware requirements, specially memory.
These days I'm not even surprised when new clients demand Go in my current consulting firm.
I think there are "better" languages than Go but they also come with their own tradeoffs and from what I've seen, to many it seems Go is preffered after weighting in.
- wikibob 7y agoThis is interesting. At the Banks was this driven by internal staff, or contractors? I’m considering contracting, any particular banks that you thought were more competent?
- hu3 7y agoIn my case the Go adoption was spearheaded by a team lead from their staff. As for what banks are more competent or dare I say modern, it can vary wildly even in the same bank depending on what piece of software each team works on. From my experience banks are (understandably) resistant to change so you might have a hard time finding greenfield projects there. In general, I'd say go for banks only if you're interested in quick money over career development. It can be soul crushing at times.
- kjs3 7y agoDisclaimer: At a very large US bank. Seconding the assessment. We have pockets of everything from legacy mainframe you've probably never heard of (no, not every mainframe is an IBM) to cutting edge cloud/docker/devops/agile/etc. Just depends on where you can be plugged in.
- isodude 7y agoWhen I was being exposed to functional programming I absolutely loved it. However, when challenged with rewriting non-functional in a functional manner, all hell broke loose. It's not a complete rewrite, it's a completely different mind set. Almost as it's simpler to just start fresh with the problem at hand. I get the same feeling with Go, if you try to copy what you've done in other languages you will be enraged. If you embrace the new mind set, it's nice. Rust is nice, but it's a fresh breath of air to not have a weird syntax to work with but proper words. But maybe I've been too far away from C for too long of a period.