Dont get it wrong i m not trying to piss you off

This is how i argue
If i am, Srry
hahaha.. not to worry, it takes far more than that to get under my skin.

I understand you dislike ioncube and that is perfectly ok. I also understand a while back, it was a pita to host any site that had ioncube encoded parts, as you needed to install the loaders yourself, and you are right, 90% of the people out there have no idea what it is let alone trying to install it. (not to mention warez'd themes would not come with the loaders or instructions on how to install them to begin with).
In practice the loaders get installed in the same folder as the encoded theme, which the php stub detects, loads and all is happy however with recent changes to the newest PHP releases, this no longer works as it allows users to install and use rouge php dl'd modules which is a huge security risk.
Because of this, website companies (for example hostgator, etc.) have had to start installing the loaders (iocube, zend, etc.) themselves which makes it easy for website operators to simply install an encoded theme, plugin, or anything else and just have it work without even knowing it was encoded to begin with. no fuss, no muss. Most website operators (companies) worth a grain of salt should have already done this. Of course any newbie trying to run a website / blog off their home DSL using IIS (gasp) would still encounter problems without the loaders.
If you were offering your own theme (not pirated) and wish to use ioncube, this would be a non-issue, as you would simply inform the person using it how to install it.
Using ioncube or zend encoding would be by far the best method to protect the code, but is also by far the most problematic. Using simple obfuscators will save you a world of trouble, but are also very easy to decode. There are pros and cons to both sides.