A look at why ARIA should be treated like any other web technology:
All web technology has compatibility issues... [and] ARIA is a web technology.
In other words: use semantic HTML wherever possible so that you keep ARIA use to a minimum; break complicated interactions down as much as possible to prevent ARIA overlapping and getting muddled; always check for support (like you would with any other web language); use automated accessibility tools like WAVE and Axe; test your code. Just like JavaScript, CSS, or anything else, it's best to keep things simple so, as Eric puts it:
ARIA should be the last tool you pull out of your toolbox, not your first.