Yes, which is both good and bad news, from my standpoint. Good because theoretically I won’t need to support it anymore, and bad because initially I expect to get calls from people saying that suddenly my applications don’t work for them. And I’ve found it won’t necessarily be obvious what is going on. Non-technical users often don’t understand what browser they are using, and I know of at least some who have short cuts to one my web applications on their desktops. I wonder what will happen when IE is gone - I expect those short cuts will just not work since I think they are set to use IE.
So yeah, WASM may be a good alternative moving forward. Although honestly, it seems like overkill for what I need. Basically these are database CRUD applications, and the data is on the server. Yes, I will do some data validation on the client, but it certainly doesn’t require heavy resources, which seems to be the kind of thing that people say WASM is good for. Also, I occasionally end up needing to use third-party components, and I fear that WASM is going to cut me off from that option.