I gave my 2010 macbook pro to my parents when I got a new one in 2015. They still use it to surf the internet and sometimes for netflix before bedtime. Its battery is so swollen that the lid cannot close anymore.
I also bought apple care but never had any chance to use it. Very impressive for a computer without any hardware failure for 12 years.
I heard its name frequently around the time before nginx came to its fame. Maybe 15 years ago. However, I never heard any major players use it after that.
I am also in the middle of moving off graphql to REST api. It is a 5 years old project and the graphql part was implemented with a very old spec. Since it has not been well maintained, it could not catch up with any features offered by graphql and users need to write their own queries by hand due to spec compatibility.
Rewriting it to REST allows us to "rebrand" these apis. At least, it does not scare our api users as the word "graphql" did.
in dev: You can setup dependencies without worrying about underlying os. So it is easier for building a new dev machine, adding a new team member, etc.
in integration test: you can setup multiple integration test environment as long as you have enough resource. Running multiple integration tests without interfering other team members is the major benefit here.
in prod: as you may know, for isolation and horizontal scaling. Easier roll back and update?