{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/c5d817db444f48ce8f30c640e585b83f\" frameborder=\"0\" width=\"3342\" height=\"2506\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":2506,"width":3342,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":2506,"thumbnail_width":3342,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/c5d817db444f48ce8f30c640e585b83f-00001.gif","duration":151.89999999999995,"title":"Why We're Scared to Break Backwards Compatibility 😱","description":"In this video, I want to discuss why we are hesitant to break backwards compatibility and rewrite oxygen. I will explain the challenges we faced in the past when we released oxygen version 2, which was not backwards compatible with version 1. I will share the feedback we received from a prominent reviewer and how it affected our reputation. Additionally, I will highlight the importance of maintaining compatibility and the potential consequences if we were to break it. Please watch this 3-minute and 40-second video to understand the details and why we are committed to avoiding such a situation."}