marled
bitflipper
As a software engineer, I am philosophically opposed to any scheme that breaks software by default, allowing it to work only after a very specific set of criteria are met. Such a design is doomed to be fundamentally unreliable, as Pace's colorful history has proven.
Also software engineer here and I totally agree to your first sentence!
But if I compare iLok with all kind of online autorisations and cloud solutions, then I am convinced that iLok is ahead! They are much more unreliable, because they have even more triping hazards.
Marc
Yet another software engineer here... and I tend to agree with Marc here.
I've never had any reliability problems with iLok. Doing a system re-install is a breeze for my iLok enabled plugins, none of this searching around for serial numbers, or fighting with online authorisation. You also avoid the nonsense of having to re-authorise after doing a Windows update, or changing your hardware configuration.
I've only two complaints about the iLok:
1. The iLok dongle is too big for constant use with a laptop. This limits me to plugins that don't require a hardware iLok, or have cloud support. My 2 desktop PC's are unaffected by this.
2. The number of authorisations available. Some vendors allow 3, most allow 2, and some only 1 (McDSP / Antares !!!). I really object to having to buy something twice (or 3 times in the case of McDSP) when everything is already locked to the same user account. I'm assuming developers have to pay PACE for the various options (i.e. hardware iLok required or not, number of authorisations, cloud support etc), but limiting licenses to 1 machine per purchase is pretty bad, considering the price of the plugins.
In saying that, the Waves authorisation is just as good/bad for the same reasons. Waves has one advantage at least, in that you can at least unauthorise without that PC being switched on.