Which one should I pick for a new project?

I can only recommend based on project fit, not general endorsement. Here's what the evidence shows:

hugeterry/coordinatortablayout

Verdict: AVOID for new projects — The RepoPilot analysis flags this as unmaintained: it's a solo project with stale commits. This means:

• Bug fixes and compatibility updates are unlikely
• Android dependencies (support.v4.view.ViewPager in the code) are outdated; modern Android uses AndroidX and Jetpack Compose
• You'd own maintenance burden if issues arise

Use case: Only if you need a collapsible TabLayout + CoordinatorLayout pattern and can fork/maintain it yourself.

lmax-exchange/disruptor

Much better maintained. LMAX Exchange is an established organization; the codebase shows:

• Active development (multiple wait strategies, stress tests, modern patterns)
• Professional structure (exception handling, event processing DSL, comprehensive testing)
• Clear use case: high-throughput, low-latency inter-thread messaging

Use case: If you need a lock-free ring buffer for event-driven concurrency (e.g., financial systems, real-time analytics).

---

Bottom line: Pick based on what you're building:

• UI collapsing tabs? Build it yourself or use modern Android Compose—don't use coordinatortablayout.
• High-performance event processing? Disruptor is a solid, maintained choice.

FOLLOW_UPS:

• What problem are you trying to solve with your project?
• Does Disruptor fit your performance or latency requirements?
• Are you building for Android or general Java backend?