FUCK ADOBE!

Out of context: Reply #70

  • Started
  • Last post
  • 715 Responses
  • fruitsalad-2

    Thinking about AEscripts, all those plugins... why has adobe allowed people to script plugins for their software? Opened that one up to the users... It's because adobe can't make the right decisions on which features to invest money and time into building, they clearly get it massively wrong. So they decide, ok, lets open up the software, allow users to script plugins and extra functionality, because that will save us money, we don't need to develop the software anymore, we can sit back and rake in the subscription cash, and users will be happy creating plugins, ha ha ha....

    Wrong adobe, wrong. What this means is:

    1 - we end up paying more money to gain the functionality we so desperately require from your software.

    2- we end up with out of date plugins and things going wrong when you do update AfterEffects adding in some random useless feature.

    3 - it means that everyone in the team, or fellow freelancers need to buy those 3rd party plugins just to work on the same project or for amends etc. = a world of pain and extra costs and incompatibility issues.

    What you should do instead, is buy the most popular plugins, and develop into After Effects natively their functionality. So that we all have the same functionality across everyones copy of aftereffects, so that we can work in teams and get freelancers in to help, without having a plugin expense of incompatibility nightmare.

    • All true but if they ever shut out 3rd party developers we'll have to burn their offices - no matter how good the next version is.CyBrainX
    • in reality plug-ins just use built-in functionalities but make them more comfortable to use.
      some exceptions got licensed by adobe and are included in AE.
      uan
    • if you chose to buy and use a plug-in you do it because it saves time and therefore costs.
      not in any case because AE couldn't do the effect without the plugin
      uan

View thread