Quote:
Originally Posted by 1nsane
I just hope you won't be completely breaking backwards compatibility by requiring the source to load plugins. This won't stop the license violators. Instead they will move on to something that is much harder to decompile and will break easier (which is a bonus in the case of payed plugins).
|
This isn't my decision to make. I don't have any strong opinion, except that it's best not to anger users - and if users want to keep running existing binary plugins, that's important.
It would stop naive license violation. If violators move on to C++ - great. No one wants to maintain or install C++ addons
besides, SM extensions don't offer big advantages over MM:S plugins.
Quote:
Originally Posted by 1nsane
Also you'll have a lot of complaints from people who lost the source to their plugins or used alternate versions of plugins.
|
Yeah, that is a totally legitimate concern. That alone is enough of a reason to nix breaking compatibility.
Quote:
Originally Posted by 1nsane
But still, I can't pretend it's a good thing just because it benefits me.
|
I like this attitude!
Quote:
Originally Posted by 1nsane
I know this was posted a long time ago on your blog, but wasn't there a considerable performance (speed) benefit in using precompiled files compared to plain source files that evenscripts uses?
|
Believe it or not, compiling from source would let us eek out - I'm estimating - another 2-3X in general Pawn performance. Loading bits out of a binary is very restrictive, you have to obey exactly what the bits say. If we loaded from source, we'd have the freedom to make all sorts of optimizations that are currently not possible.
(This is not categorically true - we could also introduce a new binary format, but the amount of work required is the same. You need a new compiler.)
__________________