Activity › Forums › Creative Community Conversations › “Adobexit”, switching from PPro to FCPX
-
“Adobexit”, switching from PPro to FCPX
Shawn Miller replied 9 years, 3 months ago 18 Members · 63 Replies
-
Brian Seegmiller
February 9, 2017 at 7:50 pmThe way I look at it is this. Third party developers can create and update there plugins faster than if the feature was in the software itself. It might not be a priority to fix a half baked in feature of the software, therefore it takes longer to fix.
-
Shawn Miller
February 9, 2017 at 8:13 pm[Brian Seegmiller] “The way I look at it is this. Third party developers can create and update there plugins faster than if the feature was in the software itself. It might not be a priority to fix a half baked in feature of the software, therefore it takes longer to fix.”
I think that’s true of all software, even plugins. ☺ Show stopping bugs can linger for long periods of time if they don’t affect a large number of users, or if it’s hard to invoke the offending behavior – these bugs can sometimes get less priority than minor UI tweaks. The other side of the coin is that, if the host application breaks the plugin and the provider doesn’t consider a fix a major priority, then the plugin developer might be stuck.
Shawn
Reply to this Discussion! Login or Sign Up