Virtual or virtual

-"I wan't a virtual app", my client says. "I wan't my app to be virtual!".

-"Fine", I reply not feeling like arguing about why and such, and I deploy his stupid program as an AppV.

-"How do I start this on my paddle?" he comes back asking.

-"Your paddle?"

-"Yes, my iPaddle!". His face is getting red.

-"You didn't say you wanted to have your program published to your tablet. I can do that, but it'll be a cost associated with it, licenses and stuff".

-"What do you mean? It's my program and it's my paddle!"

-"Yes, but it doesn't run your program, a program you have developed in Visual Basic, now does it?"

-"No, but I told you I wan't you to make it virtual!". The shade of my clients cheeks are now turning into a blueish color and his forehead is sweating. "Virtualize it!"

-"I did. But I now understand what you really want is a published remote application. I can do that too, but as I said, it needs an infrastructure that costs money. I can still do it, but I need one or a few servers and software that costs more or less money, depending on how many people are going to run the program among other things".

-"It's just me, on my paddle! And I don't care how you do it, I don't know the mumbo jumbo, that's YOUR job!"

-"If you don't know the jargon, why did you specifically order a virtual application, instead of just telling me what you want?"

True story.