Hacker News Reader

I would argue that gRPC and Kafka is "general knowledge" in the sense that these are language-agnostic. In other words there is no requirement "Go language knowledge," but a requirement "gRPC and Kafka knowledge."

View on HN

It really isn't. It's very much tied to certain stacks, while it's completely uncommon in others stacks, because they're solving the same problems in a different way. I've never touched it in my life. Sure, I can pick it up, but I fail to see how it should be considered common.

I see your point, but I still don't think you can just say "If you want to get a job as a Go developer, you must know gRPC." Even more so for Kafka, I've only heard about it being popular in the Java world. You can't even say "If you want to get a job as a Java developer, you must know Spring." Nowadays, sane Java projects use https://vertx.io, it's just too good. I would argue that Spring is for legacy projects only.

> You can't even say "If you want to get a job as a Java developer, you must know Spring."

Majority of job postings say otherwise.

(Any sane Java projects use Quarkus (which is build on top of Vert.x, but that’s besides the point))

> Majority of job postings say otherwise.

Isn't it because the majority of job postings are for legacy projects?

Also: glad I'm not the only one who uses nested parentheses.

Reply on news.ycombinator.com