3 ms·
I feel you. Mid-30s Java lifer here. I got way more pessimistic as I got older: bugs are here to stay, bosses will keep their buddies and fire trouble makers,
by mrkeen 4y ago
I feel you. Mid-30s Java lifer here.
I got way more pessimistic as I got older: bugs are here to stay, bosses will keep their buddies and fire trouble makers, the project will be wrong the first time, need a costly rewrite, and won't be used once it's finished.
Just drink the Java and spit out the stack traces.
I do my Haskell & Rust in my own time now. (Not quite true - I always tinker with some kind of Haskell at work - my own productivity tools).
Btw, what did you like about Go? Wasn't it just Java-without-generics-or-exceptions-oh-wait-we-need-first-order-generics ?
- John23832 4y agoJava just feels like ditch digging to me. I've done Java for a long time (since middle school), but as I've gotten the ability to build things in languages I can actually choose (read: languages I like) the prospect of going back to Java ditch digging really sucks. Even as this current startup starts to die, I'm starting to build the basic infra for my own startup in Rust. As for Go, I really like it as a language. It's a good language for beginners, imo. The syntax is easy, semantically it makes sense, async support is really good out of the box, and the community is big and well maintained. I've done it professionally for 4 years now (with a 2 year stint that took me back to java... the impetus of this post). I really haven't needed to use generics in Go honestly. I fall into the "interfaces are the generics of go" camp. Going forward I'd personally prefer to use Rust over Go. I find the semantic concepts and memory management more intriguing.