Ruby definitely is simpler and I agree on the horrendous node_modules issue. However, there are a few things that you don't cover. RubyGems isn't as flexible as NPM. With NPM it's possible to define scripts in the package.json. With Ruby, you'll have to install Rake and use that. You also need to install a bundler to make package installation more convenient. I get that you're trying to show an example of how easy it is by saying that you only ever need to install 2 packages for your E2E tests. But in reality, this isn't the case. You'll eventually need to install different packages depending on the work you're doing. What if you need to generate a random 128-bit UUID? What if you need your E2E test to work with a Cloud Provider? What if you need to use a special SDK for your tests? Everything will have tradeoffs. Cypress has a great UI for writing and debugging tests. But it's painful to work with sometimes. Playwright runs has a nice recorder for tests. Puppeteer is straightforward, but the learning curve is high. WebdriverIO somehow made Selenium harder to work with.