That information is several years out of date. At best, the build tools in the ecosystem don't do a great job of supporting modules, but that's about it.
And your comment about `jlink` MIGHT be true if your application is nor modular/ does not use modules with a well-formed `module-info.java`. I haven't tried an automatic module in a long time. If your application is modular, everything happens as expected. I do this for all the builds for all of my projects. Last build from last night confirms that it still works, and works well.
Last time I checked, jlink tool refused to make use of those "automatic module" dependencies when creating an image.