Quote:
Originally Posted by nenad007
A closed source most of the user don't like I think, there are many reasons why not, like the user don't know whats the web app doing (bad coding, open backdoors or whatever), whats happen when a new php/apache version coming out and what's with the performance, yes it's great that you used some well cache solutions in but on every request many times ioncube engine need to load the code, with 10 req/sec for sure no problem, try with 200 req/sec and more. Or whats happen if the vendor stop his business? and and and.....
Who tell you that Ioncube is not hacked? Official since November 2004 a easy way was found how to decode the source out from ioncube encoded source.
To decode this 223 files in the tar it takes not more then 15 min.
OK, you used the new feature of ionCube 6.5 to Obfuscate the Function and variable names of the code, this makes the reverse engineering harder, with some experience 10 hours later the reverse engineering is finished.
|
We are here for many years now and no plans to leave :-)
I know anything can be hacked, i was in the hacking scene for years and nothing is save, i am fully away of that, but still we want to protect our source as much as possible, we put years of work into this so why just hand it to people.
But yes you are right, some don't like STP's closed source, but those are not the people that buy it. The people that buy it already know what features they want and what STP offers.
STP is very very customizable and already has loads of the most important features, if we feel there is a need for a feature we will add it by popular demand.
This is the path we have chosen to go and time will tell if we took the wrong one or not.
If people want open source than they know were to go, Konrad is a great guy and we have high respect for him.