I haven’t used it, but I believe the vision was it would provide some assets stock, sell some more, and also allow import of your own. Could allow for random encounter map generation when you need a quick setup as well.

It’s not a terrible idea, it’s just one that was unlikely to be executed well under WotC and Hasbro.

If they can get Beyond back into as good of shape as it was when they bought it, I’ll change my opinion of their management. Until then, they just don’t seem to have the vision necessary to keep digital projects like this going.

There’s a lot of good reasons. Notably, web apps have better security by running within a browser container. And they run anywhere that has a standards-supporting browser. And most desirable to me, it obviates the need for Electron for many of the apps using it right now.

Oh, and most importantly for mobile, they are more privacy respecting than running e.g. the actual Facebook app.

The Bangle.js is around too.

Chromium is code that Mozilla is not familiar with and has a reputation for being poorly documented.

A fully divergent fork isn’t likely to make development any easier for Mozilla. And a soft fork puts them at the whims of Google’s development decisions. If Mozilla needs to pivot, joining with WebKit seems the more feasible option, though that would also likely be a battle to keep a Windows port maintained.