|There's more than one way to do things|
The most important difference between require and use when importing them is namespace control.
Prior to Perl 5 you would require libraries to import everything into your script's namespace. Libraries would then potentially clash with both your own variables/subs and those of other libraries. Those libraries would typically have the extension .pl
In Perl 5 this was solved by adding namespaces that spring into existence whenever referenced, and modules imported by use are by definition packages that have their own namespace. Only by explicitly exporting stuff into your main namespace can they cause problems. Modules to be imported with use must have the extension .pm.
Well-written modules let you control what gets exported like this, for example this would ask the Foo plugin to put "bar" and "baz" (and nothing else thank you) into your main namespace:
Another thing you will often see is modules offering a set of definitions as a group, those group names typically begin with a :colon. This reads as "give me everything needed for using that feature". But nothing else, please.
Ofcourse, badly written modules exist, this is more of a guideline than a strict rule.
Because namespaces matter so much, you're really not supposed to decide yourself how to import stuff written by others. Just as you can use a flathead screwdriver on a philips head, there are always ways to make a module work using require (and with some hacking, vice versa) but it doesn't make you look very professional and you will end up breaking stuff in the long run.
Time flies when you don't know what you're doing