3 ms·
"which has a couple "800 pound gorilla" projects, but then it falls off pretty quickly." Better to depend on numerous 800 pound long-lived gorilla's than a mil
by lenkite 4y ago
"which has a couple "800 pound gorilla" projects, but then it falls off pretty quickly."
Better to depend on numerous 800 pound long-lived gorilla's than a million short-lived mayflies that keep dying.
- throwawaymaths 4y agoWell those gorillas are really hard to maintain. Suppose you found that it wasn't quite what you wanted. Would you poke your head into the Kafka codebase?
- lenkite 4y agoJava Gorillas are far, far easier to maintain than JS mayflies. Static typing, top-notch refactoring tools, excellent IDE's with deep language analysis, stable ecosystems, minimal dependency chains, better performance, better profiling tools, trustable repositories with well-supported choices for self-hosting - the list goes on and on. PS: I have already poked my head into the Kafka codebase in the past. Not the best written project and also confusing because of the Scala mix, but far more readable than several I have seen. And Java makes it easily navigable. Can even auto-gen diagrams to grok it better.
- hn_throwaway_99 4y agoMy point was that JS has its 800 pound gorillas too, and so if you only want to use that, you can. But it has so much of a broader ecosystem of other tools that if you're willing to take that risk it's an option. Java basically just doesn't have that.