That's a vast question. Personally, two: - as a freelancer, new business use-cases. We're essentially bridging OS with browser in terms of capabilities at that

That's a vast question. Personally, two: - as a freelancer, new business use-cases. We're essentially bridging OS with browser in terms of capabilities at that point. I find that there are often a few low-hanging fruits in pretty much all categories of tech that you might do well to leverage, with parsimony. Some of my potential projects tend to have unrealistic demands for the budget (hence they remain "potential"), or actually, for the times, and wasm is moving the needle in that regard. Think, do the 20% that yield 80% of the result and integrate that into a classic stack. Baby steps. Low-effort, high-value 'features', you don't need to rock the boat to benefit greatly from the addition of wasm. - Research: some of it may be gimmicky today, but I wager it'll become the standard a decade from now: web = OS = native, in the user's perception. Note that it won't end "platforms" (horizontal business-driven gardens, e.g. darwin-safari, gentoo-chromium, etc). We're talking about a vertical bridge here, "through" the hard+soft stack, from kernel to browser passing by storage, GPU, sensors, at last SMT, etc. It took us what, 30 years, but we finally reach a point where web and native may become technical finer points, not a user experience gap. So wasm now is already a great enabler of feature-rich user experiences, and that has value to me. It's also a big part of the next paradigm, IMHO, thus worth wetting the shirt as soon as possible.