Nothing has changed between MySQL 5.5 and 8.0 to make ENUMs any more or less evil than they were before.

I think "evil" used in the blog you linked to is hyperbolic. A programming language feature isn't evil. But it can be misused by developers who don't understand its downsides. Then they run into trouble.

If the ENUM columns you have are working well for you, and your current project has not suffered from the downsides, then there is no reason to switch them.

It's a good thing to keep the pros and cons in mind when you design new tables. Using an ENUM in one table may work fine, whereas using it in another table in the same project will run afoul of one of those issues. It depends how each table is used.

I wrote more about ENUM in a chapter of my book SQL Antipatterns Volume 1: Avoiding the Pitfalls of Database Programming.

Nothing has changed between MySQL 5.5 and 8.0 to make ENUMs any more or less evil than they were before.

I think calling it "evil" is hyperbolic. A programming language feature isn't evil. But it can be misused by developers who don't understand its downsides. Then they run into trouble.

If the ENUM columns you have are working well for you, and your current project has not suffered from the downsides, then there is no reason to switch them.

It's a good thing to keep the pros and cons in mind when you design new tables. Using an ENUM in one table may work fine, whereas using it in another table in the same project will run afoul of one of those issues. It depends how each table is used.

I wrote more about ENUM in a chapter of my book SQL Antipatterns Volume 1: Avoiding the Pitfalls of Database Programming.