I like PowerShell too, but in what universe other than ours (clearly the worst one) is it even possible for loading a module to take more time than the blink of an eye?
Microsoft should find it embarrassing how long it takes powershell to load a module. Pushing <tab> to autocomplete a cmdlet name should never take more than maybe 100 milliseconds.
Loading times surely is not a problem unique to Powershell. The more complex and advanced a software gets, the more it takes to load data into RAM that appears to the user redundant.
This is the most noticable with startup times. My favorite software (Firefox) has this solved; it opens up in reasonable amounts of time, even if it takes a moment after to show the first website. My second favorite software (Inkscape), meanwhile, takes so long just to show the main UI that the developers didn't think anything of adding a splash screen: an overt acknowledgement that you're keeping the user waiting.
I, too, wish that everything were more lean and snappy, but clearly this is still an unsolved problem.
It is amazing until you run into one of these insane behaviors that somehow nobody ever fixed.
(Some are actually fixed finally in 7.x - like issues with filenames with grave characters in them)