"Easy to pull 3rd party libraries" is not particularly positive for a engine/library developer; ideally, you should incur as little dependencies on your users as possible.

Why?

There are outstanding ecosystems for packaging and dependency management in place. That makes it easier to embrace than to avoid dependencies as a library developer.

A library can't depend on other libraries unless there's a strong guarantee that those other libraries will work everywhere. If you go using tons of dependencies, you limit yourself on porting. If you go crazy with apt dependencies, you've probably just limited yourself to Linux, and end up with the opposite problem as shown in the article.

That's true, honestly, library installation is a pain on Windows. Sadly, the problem on Linux is often Driver installation, which is more problematic to be missing.

I would suggest that on windows you copy all the relevant libraries and headers to your project root and use those, rather than try to "install" them.