We wrote E2E tests with Cypress before Playwright was around and it was awful. The API is weird to the extent that it is basically a DSL based on Javascript. And the tests were flaky because rerenderings could happen between Cypress getting the DOM element and interacting with it. It seems they haven't fixed that one to this day.[0]<p>The team is also very confident about their approach. They build their own asynchronous concepts that are not interoperable with async/await, openly acknowledge that it is hard to wrap your head around and then dismiss these concerns by asserting that "Asynchronous APIs are here to stay in JavaScript.".[1] The Github issue about the lost DOM elements is also full of answers by a team member intent on writing blog posts that explain what the user is doing wrong rather than fixing the root problem.<p>I'm really glad that Playwright came around. It is intuitive, pragmatic and has none of the problems above.<p>[0]: <a href="https://github.com/cypress-io/cypress/issues/7306" rel="nofollow">https://github.com/cypress-io/cypress/issues/7306</a><p>[1]: <a href="https://docs.cypress.io/guides/core-concepts/variables-and-aliases#Return-Values" rel="nofollow">https://docs.cypress.io/guides/core-concepts/variables-and-a...</a>