Cypress breaking on every deploy is not a cypress problem and it never was. Tests written against class names that change every refactor, hardcoded IDs that get swapped out, selectors that have nothing to do with what the user actually sees or does, that is the root of it. Switching tools without fixing that mindset is just rearranging furniture in a burning building and the framework gets blamed every time because it is easier than admitting the whole approach was wrong from the start.

That said there are real architectural differences that matter depending on the use case. Playwright's parallel execution is genuinely better for larger suites, cypress has a better debugging experience when tests do fail. Neither solves the core problem of tests written against implementation details but one of them will waste less of your time depending on how the team writes tests and how much CI time actually costs.