Hey
@Kartik Agaram! Good question, one I asked myself many times during the last year 😂. In the last 60 days, 251 people edited code, and 471 canvases had more than 10 requests.
The way I looked at bug-for-bug compatibility is that each different thing could cause some edge case somewhere, and that it was hard to enumerate whether those edge cases were ok or not, without doing to work to make it bug-for-bug compatible.
There were also some secondary considerations:
• learning how to actually keep dark compatibility promises in the long term
• learning what rabbit holes existed in the codebase
• the “marketing” goals of dark (in particular in
https://blog.darklang.com/how-dark-deploys-code-in-50ms/)