SQLPS really should be deprecated. It's a really limited version of Powershell designed to just run the SQL modules. Making that into a module to use with Powershell makes a lot more sense. Add this new module to Powershell and you'll have the full functionality of Powershell along with the SQL functionality. I remember being somewhat frustrated trying to use the full functionality of Powershell w/ SQLPS and searching for the instructions to just add that to the native Powershell within my profile. I did that and have been pretty content since. There's a learning curve, but it can be really useful for automating some DBA tasks, doing audits, and even to semi-easily mix database calls with DLL calls in one interface. (If I can do it, it must be somewhat easy
I will admit that the SMO docs and examples have been shaky, but I have found a little more help with Powershell calling SMO. While it doesn't necessarily make it easier to use, the examples have been a bit more stable and have been written by people who needed a solution so generally work.
And Jeff, MS is trying to give us job security again. Remember when SQL Server was so easy it didn't need a DBA?