Thank you for the thoughtful feedback! I'm happy to share my perspective on Temporal vs Cadence.

Cadence was Temporal's foundation. It pioneered many core concepts of workflow orchestration. Temporal has evolved to become more friendly to developers and more versatile. Its modern API and docs make it easy to build robust, distributed apps.

Temporal's multi-language support is very valuable. You can write workflows in Java, Go, PHP, or TypeScript. It ensures consistent behavior in any environment, whether cloud or on-premises.

About your suggestion for covering Temporal pitfalls - that's an excellent idea. I want to write a practical guide. It would explore real challenges, like state management, versioning, and performance optimization. I'd base it on my experience. Sometimes the trickiest issues emerge around activity timeouts and workflow coordination patterns.

Are you interested in discussing specific pitfalls you've encountered while working with Temporal? I'd be curious to hear about your experiences.