3 ms·
That was my understanding too. What's the use case here? I'm hard pressed to think of something big enough where UI automation is too slow, but it isn't a bet
by ethbro 9y ago
That was my understanding too.
What's the use case here?
I'm hard pressed to think of something big enough where UI automation is too slow, but it isn't a better idea to re-architect the process to not use MS Office or consumer apps.
Maybe finance? I'm sure they've got enormous Excel files...
I work in this space, and individual COM implementations are pretty bad in terms of development effort : utility. Because at the end you have one, single purpose function.
- TimJYoung 9y agoI think it's often easy to underestimate just how much VBA-type code has been written around the MS Office suite of applications since the late 90s. It's a massive amount of department-level (or higher), home-grown code that leverages the MS Office functionality in lieu of paying professional software developers to develop something more streamlined, but much more expensive.
- ethbro 9y agoDealing with that is a big part of my day to day. ;) My point being that for everything but performance critical use cases, generic UI automation works well. So was trying to think of situations where 1) performance requirements were higher than UI automation could deliver & 2) performance requirements are low enough that it doesn't make more sense to rewrite the code in a more appropriate system.