How and why do you use Cypress if it doesn't support either Safari or mobile browsers?

Question

Software testing

I noticed that many people praise Cypress, and he is often in vacancies.
Like, this is the future, and it's time to slowly put Selenium on the shelf.
I'm all for it, I like this framework.

But still there is a very important point in which my logic, as usual, diverges from the opinion of the majority.
Cypress doesn't support Safari, and doesn't even intend to support it much.
We go here and see a cross and "Not under active development".

But in my opinion, it is Safari that needs automation first of all. In Chrome / FF, you can also test it with your hands. But Safari - well, if you don’t have a macbook, then in practice you most likely won’t even go to your site from Safari, let alone test it. In addition, what works in other browsers most often does not work in Safari (well, except for IE - a browser that you definitely need on the shelf).
The same goes for mobile browsers. Again, you need to test: it sometimes surprises. But it's difficult. Fingers and eyes are very tired, a separate person is needed. Or a separate "robot" replacing a person.

Cypress can do neither.
And so the question is - why, in fact, are you using it? And how do you use it? Do you have a project that does not need to support either Safari or mobile browsers? What am I not understanding, what is the error of my logic?

Answer 1

About mobile and safari - it first of all needs testing, but not necessarily automated.
And then only if a lot of users of the site / target audience are sitting on it.
That's why the question is not on that side.
Automation, kmk, is primarily needed to run a large number of tests, which, in principle
, a person cannot pass in adequate time. Or get tired and make mistakes.
And all sorts of jokes that pop up on all sorts of exotic browsers - you can check them with your hands