Squeezing the process
I wonder when they will come up with licenses that charge by-the-instruction as to how many clock cycles you are using in your program.
Then, when you think you managed to have optimized your programs, you will be faced with a memory tax. The first 640k are for free, every next kByte(*) will cost you a relative fortune. Cache memory will be at least twice as expensive.
When we apply Moore's law to licensing, then we'll see licenses to charge per electron set into motion to optimize license money extraction. Counting the electrons will be, of course, charged to the customer because more electrons were set into motion in the process of accounting for the electron motion(**).
(*) The courts will have to decide whether that means kilo- or kibi-Bytes after a couple of years of litigation.
(**) Recursive money machine detected. Party for ultimate wealth accumulation is in preparation.