Collaborative editing: OT vs CRDT for real-time document collaboration

we're building a collaborative editing feature for a new developer tool, aiming for something like google docs, and the big architectural decision is between operational transformation (ot) and conflict-free replicated data types (crdts). ot seems to require a central server to mediate operations, which can introduce latency and a single point of failure, but it's well-understood for text editing. crdts offer a more distributed, peer-to-peer friendly model, which sounds great for resilience and offline support, but they seem significantly more complex to implement correctly, especially for rich text where the 'state' is not just a simple string. our use case is for 10-50 concurrent editors on a document. what are the practical implications and trade-offs of choosing one over the other in terms of implementation complexity, performance, and maintenance for a real-world product?