>>Another way to skin different versioning cats is to compile into COM dll, as the COM dll will load their own runtime - but at the cost of tenfold calling time due to marshalling across thread/process borders - can be critical if "Chunky, not Catty" rule is not followed ;-))
>
>I think you meant "Chunky, not Chatty". In English "Catty" means something quite different ;)

I know - but was typing on notebook keyboard, not big one ;-))

>
>I remember many years ago reading a Calvin Hsia blog post about improving performance of COM automation, which basically discussed this (marshaling). I haven't been able to find it, maybe someone else has better Google-fu.
>
>I think that post would also address Albert Gostick's question in another thread.

Yupp, although I think that while the term is often read correlated with COM, it should be seen as "leaving own runtime", with consequences all the more markable the more different parts like variables, datatypes and so on differ form the 2 involved runtimes.

On a side note - JS and WASM representing "traditional" static (value) typed vars moving towards each other is something seldom seen before. The only comparable thing I worked with was the CPython/Cython integration, where the user could move more and more work into the C-runtime for parts getting a boost there.