That's all fine and dandy until the day comes at MSFT stops maintaining the WSL subsystem and/or lets subtle incompatibilities creep in.
Bring it up with Microsoft? What do Windows app developers do when Wine doesn't run their application correctly?
How does it compare to offering a build linked against the Cygwin library?
Zero extra work and no need for a separate box or VM, and a Windows licence, to test the build.
Let's not forget the effect of helicobacter pylori bacteria on ulcers, they are in general held to be the main cause these days.
I have another theory about the beneficial effect of aspirin, caffine, etc. We evolved with them. Our diet was rich in salycilates and chemicals similar to theobromine or caffine. They came from the plants we ate, some of which were mildly toxic and which we evolved to process to the point that we became dependent on some of their effects. There are a lot of things in the primitive diet that modern people don't eat much at all, like acorns which had to be soaked to remove alkalai and tannin.
If this is the case, taking aspirin and drinking coffee or tea replace substances found in a more primitive diet.
If this was a drone and was just using the mobile frequencies for communication, it would probably use an off-the-shelf cellular modem module to communicate normally over the cellular network. A special testing authority from the FCC would not be necessary.
Sounds horrible to me. Why bother?
Not sure what MS' motivation is, but it's good news for a lot of scientific software developers. Small teams or single researchers rarely have enough time to even keep the main development going, never mind keeping up with multiple OS targets. With this everybody can simply focus on Linux, and tell Windows users to just run it under the Linux layer and stop asking about a native port.
"The vast majority of successful major crimes against property are perpetrated by individuals abusing positions of trust." -- Lawrence Dalzell