3 ms·
AHK [0], Sikuli [1] , and Ui.Vision [2] are extremely limited vs what a proper RPA framework will give you for Windows automation. If your needs are minimal (e
by ethbr0 6y ago
AHK [0], Sikuli [1] , and Ui.Vision [2] are extremely limited vs what a proper RPA framework will give you for Windows automation.
If your needs are minimal (e.g. test automation, because you don't care if it breaks 10% of the time), that's probably enough.
But they're definitely not the same class of tools.
[0] https://www.autohotkey.com/docs/commands/Control.htm https://www.autohotkey.com/docs/commands/Control.htm
[1] http://doc.sikuli.org/match.html#Match http://doc.sikuli.org/match.html#Match
[2] https://ui.vision/rpa/x/desktop-automation https://ui.vision/rpa/x/desktop-automation
- eastendguy 6y agoI have used all three and none of them "breaks 10% of the time". Why would it? Of course, these tools are more lightweight and lack the advanced scheduling, monitoring and robot distribution features ("Orchestrator") that UIPath offers. But if one needs only straightforward task and test automation they are a good and reliable alternative.
- ethbr0 6y agoAmong other things: Citrix remote app compression, resolution changes, screen magnifier software for users with disabilities, lock screens. These are all things I've had break visual matching in prod deployments. The scheduling, monitoring, and distribution are (IMHO) the least interesting parts of UiPath. They're pretty trivial to build with other tech. But a matching engine that offers a plethora of high level rule options, coupled with deep inspection capability, and fast runtime matching? That's a pretty big building block.