Something on PM to direct and help deploy is kind of a must for your work to scale to customers who aren’t in direct contact;
With respect, i dont agree with this. Look at the app ecosystem: There is an “Autodesk App Store,” and of all the apps we use, i think MAYBE three came off the app store. The rest were all downloaded straight from the manufacturer. Nothing is inherently “better” about the ones coming from the App Store, either. The Package Manager may be convenient because its “on the fly” but that convenience is superseded by the fact that its CAUSING a lot of the hardships.
Most (nearly all) companies don’t manage shared parameters or families across the org (never mind Dynamo packages and graphs), and VERY few do so as well as @Aaron_Maller does (
sarcasm: going forward all graphs I send to him will have a node in custom package that isn’t on package manager but is absolutely integral for functionality of the graph /sarcasm ).
On this, we agree. And thats the point: If an organization (even like ours) is frustrated with the complexity of it, the status quo doesnt work.
I also think- in trying to solve some of these things- the Package Manager (and the newer extension for Packages/Dependencies) are making things worse: Like, i sympathize with what this dialogue is trying to do:
Hey! Someone put the node in with an older version of Rhythm, but this isnt the right version of Rhythm! What should we do?
But guess what its actually done? Its desensitized us to even checking this dialogue, because i know if i start selecting options from that, i might get a dumpster fire reaction. Well, and it wont let me do it anyway, as itll want to uninstall the other rhythm, and- oh, oops- now restart Dynamo and try it again, etc. Allthewhile it SHOULD be asking “is the node working correctly? If so, it doesnt need to warn me here.” I know thats a tougher ask, but here is the reality:
Developers like John are getting forced to keep releasing updates, and… now were warning users because a developer released an update? So now were teaching users to ignore warnings about updates, because… everyone has to update?
The more i think about it, the more im looking forward to more of the good package developers releasing their own installers.