TXV

So far I developed my GraphQL server in Java, but it's 2 years now that every single time I try to upgrade the dependencies, I fall down a rabbit hole of mysterious errors, JDK incompatibilities and inscrutable stack traces. Frankly I'm a bit tired of debugging it. I would like to migrate to Go, which is what the rest of my codebase is written in.

Which Go GraphQL server library would you recommend, and why?

Our current codebase is written in Go, mostly web servers, middleware and queue workers. Some of Rust strengths (memory safety, concurrency, absence of GC) look well suited for our problem domain. We currently have the opportunity to overhaul part of our system to reduce some legacy technical debt, so I'm wondering if it makes sense to rewrite in Rust. I'm not looking to solve a specific technical challenge. Just curious. So, if you migrated from Go to Rust, I would love to hear about your experience.

I happened to come across a post from a moderator (-> dang) highlighting HN's mission toward intellectual curiosity.

In their comment history, dang frequently (and adamantly) states that repetition and indignation are diametrically opposite to intellectual curiosity.

I find this concept very interesting and I would like to read more in-depth scientific or sociological analysis about it, e.g. why indignation stifles curiosity, the psychological roots of this dualism, how indignation works in mass society and media, etc.

Thanks

I'm a Golang developer based in western Europe with around 5 years professional experience. I frequently receive unsolicited messages from recruiters, mostly on Linkedin, introducing this and that amazing job opportunity. Right now I'm happy where I am, but I won't mind hearing them out if said opportunity is especially compelling.

I'm not sure how to engage with them in an effective way. My goals are basically two: 1. avoid wasting time 2. avoid coming across as arrogant - they are doing their job and their time isn't worth less than mine.

To know if their opportunity is compelling I need to get some key information upfront, e.g. what's the client's budget. I don't want to even start discussing anything if it turns out that the client pays 25% less of what I'm making today. Of course money is not my only concern, but it's still a very easy way, and a very relevant one!, to filter out jobs that have no chance whatsoever to fit my definition of compelling. Another deal-breaker would be a company that doesn't allow any form of remote work. Also some of them absolutely want to talk over the phone and I don't feel comfortable with that.

So what's your strategy for dealing with recruiters? Do you demand employer information upfront? Do you ignore them? How do you interact? Thanks!