28 ms·
Even if so, they might introduce different dynamic on the same core feature. Also, core plugin system evolves and majority of the time does not support "older"
by majkinetor 7y ago
Even if so, they might introduce different dynamic on the same core feature.
Also, core plugin system evolves and majority of the time does not support "older" plugins.
I had this problem in basically any software I used with plugins be it Winamp, Redmine, FL Studio or whatever.
- z3t4 7y agoNot an issue if there are no third party plugins. Its however hard to resist allowing third party plugins when you already have the architecture. Also hard to resist feature bloat when adding new features are seemingly free.
- majkinetor 7y agoIf there are no third party plugins, then you don't have plugins - its an internal architectural decision, not relevant for the end-users. Having plugins means anybody should be able to create one. I remember vagrant has support for all historic plugins versions no matter the current API version. This is rare goodness but prevents only one type of problem - inability to update the core.