Conversation

Notices

1. Magister Endomain (endomain@hackers.town)'s status on Friday, 23-Dec-2022 04:22:30 JST Magister Endomain

   I wonder what the world is like if WebAssembly and some sort of very specific and highly limited browser subset becomes the primary way to make GUI apps.

   • Xerz! :blobcathearttrans: (xerz@fedi.xerz.one)'s status on Friday, 23-Dec-2022 04:45:07 JST Xerz! :blobcathearttrans:

     in reply to

     • Adrian Cochrane
     • Xerz! :blobcathearttrans:

     @endomain @alcinnz There’s also the part about where you put dynamic code. His approach afaik, for instance, is merely considering the option of running WebAssembly as extensions, whereas I think that there should be a bigger focus in execution termination and granular permissions on top of the memory constrains WASM provides

   • Xerz! :blobcathearttrans: (xerz@fedi.xerz.one)'s status on Friday, 23-Dec-2022 04:45:12 JST Xerz! :blobcathearttrans:

     in reply to

     • Adrian Cochrane

     @endomain reminds me of what @alcinnz is trying to achieve with Rhapsode? Agreeing on the subset is the hardest part tho imho – I’m sure CSS is where people will put up the most fights, yet it’s my favorite thing about the web and my biggest concern is its use for antipatterns and other abuse

     Adrian Cochrane repeated this.