We're using a lot of WSL in CI - we're mostly Linux based, but for some stuff toolchains came up which didn't work nicely with wine (like MSVC). So for us we want a Linux system that seamlessly can execute Windows stuff in a Linux based build process. WSL1 can do that, WSL2 can be kicked into working somewhat, but needs quite a few ugly workaround as they're not sharing a process namespace or file descriptors. While the faster IO would be nice that's pretty much the only thing we'd care about - and wouldn't work here, as we need shared access to the files. And while we could access the WSL2 files from Windows side that's even slower than just using WSL1.
https://clang.llvm.org/docs/MSVCCompatibility.html
https://llvm.org/devmtg/2014-04/PDFs/Talks/clang-cl.pdf
XWin for the CRT/SDK:
https://github.com/Jake-Shadle/xwin
https://jake-shadle.github.io/xwin/
A while ago I got some Python C extension modules building using this approach, but didn't push it any further.
I do wonder if there are any DOS vectors that need to be considered if such a large image can be defined in relatively small byte space.
I was going to work out how many A4 pages that was to print, but google's magic calculator that worked really well has been replaced by Gemini which produces this trash:
No Gemini, you can't equate meters and miles, even if they do both abbreviate to 'm' sometimes.0: https://news.ycombinator.com/item?id=36994418