In my case you are most definitely correct. I have no idea about the differences between parallelization and asynchronous programming, and would either term to describe splitting up a process in multiple threads to speed things up.

For example: one of my applications visualizes products on shelves, and the user can do a variety of actions to move products to different locations, assign more space, reduce stock, etc. Each time this happens, there are a series of calculations about the spatial, stock and financial consequences. The app now processes product by product serially, which is not a problem when there are a few, let's say less than 100. However, when you're taking 600-1000 or even more, small delays start to become noticeable. What I envision being able to do in twinBasic at some point, is to have the calculations done for multiple products simultaneously. Keeping things snappy even if there are larger numbers involved.

Even with drawing there may be opportunities I’d think. Drawing is done in multiple layers, so they have to be done in a specific order. However, it may be an option to separate the layers in different objects, draw these simultaneously, and then at the end combine the layers into one picture.

So, these days I am programming in VB6, thinking about redesigning things for the future, and learning new things. And that for sure is done asynchronously, and not parallel.