3 ms·
Why not just use the JVM and concurrency? I routinely parse 300+ GB of geospatial data without breaking a sweat using a very simple combination of concurrent li
by pookha 3y ago
Why not just use the JVM and concurrency? I routinely parse 300+ GB of geospatial data without breaking a sweat using a very simple combination of concurrent linked queues and cached thread pools. I couldn't imagine diving head long into some new esoteric language just to do something as simple as what this author is describing. And things are only going to get easier with Virtual Threads...If I'm doing something boring (parsing data) I'd just want to use a boring standard language I guess (Java).
- devjab 3y agoJava isn’t really something we want to work with. So I guess that’s the quick answer. There is nothing wrong with Java, I think projects like quarkus is pretty cool and the JVM is a battle tested machine. Our issue is more process related. We’re a small team so we try to use as few languages as possible, and since we can’t realistically avoid using TypeScript we tend to use it everywhere we can. Then when we need some extra juice we turn to C. We even PoC’ed Rust but decided it wasn’t “boring” enough for us yet. Aside from that it can be hard to hire people for Java around here. It’s not a language a lot of people want to work with, and it’s common enough that the ones who do already have jobs.