The possibility of a library lock-in -- as with most technology advances -- would likely be a short first-mover advantage. Before you know it, vanilla versions will show up by producers who go vender neutral. Technology tends to open up after an initial proprietary advantage.
And often when a library is created it allows certain variables to be changed and/or adjusted and other variables have to be considered constant. So even though it might be helpful to expand in some areas it can actually limit concepts in a different direction. As well as the comments from Alex regarding becoming too focused or specialized for one vendor.
However, I have to admit I would love a vendor to suggest creating a special library for all of our parts/systems that would allow us to work more effficiently.
I think it probably depends on the vendor and the approach they're taking. I'm not 100% certain, but I think Maplesoft's support of the Modelica standard probably helps alleviate some of the lock-in because it is a broader, industry wide standard so there is likely more opportunity for cross pollination.
How much of an issue for users is library lock in? In other words, getting too deep into one vendor because you've invested so much into either their components and libraries and/or third party tools/libraries etc.
California State University, Chico was the first school in California to offer an ABET-accredited degree program in mechatronic engineering. Now its California Mechatronics Center works with industry on machinery, robotics, and surveillance vehicles.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.