Conversation

Notices

1. Embed this notice
   Miaourt ✨ (miaourt@raru.re)'s status on Friday, 24-May-2024 03:08:46 JST Miaourt ✨

   Wait wtf wasi no don't also take this path :neocat_sad:

   https://kerkour.com/webassembly-wasi-preview2

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 24-May-2024 03:20:01 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @Miaourt Best design is to provide an atomic thing and then stop.
     
     A language to describe an ABI could be neat, but it ought to be another project entirely. And I think the only realistic way to do it would be as a subset of C. (Which reminds me of how C++ screwed itself so badly that most C++ libraries use C headers)
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 25-May-2024 04:42:40 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Ignas Kiela
     @ignaloidas @Miaourt Even beyond implementation design: Parsing a C header can effectively only be done by a C Compiler (Go got bitten hard by this many times) and in some cases the same C Compiler as the one used for compiling it. Gotta love people not making the public headers pretty much static.
     
     And yeah I've done my fair share of JSON over HTTP/TCP/socket/pipe/… it's fine for batch/timesharing things but if you ever need something with a tiny bit of real-time, you're screwed.
   • Embed this notice
     Ignas Kiela (ignaloidas@not.acu.lt)'s status on Saturday, 25-May-2024 04:42:41 JST Ignas Kiela

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @lanodan@queer.hacktivis.me @Miaourt@raru.re if anything, restricting ourselves to things that C can easily represent is a mistake, because C can't represent shit.
     
     You can't get any kind of guarantees on memory management, behavior, etc in C - that shit has to be done manually in C, and it fucking sucks.
     
     I cannot throw a Python object into C and just trust that it's refcount will stay correct - even though that could be done with Rust or Ruby.
     
     C is the shit underpinnings that keep language interop so shit that the industry recognized way for language interop is HTTP - and it's not good language interop, but at least it will fucking work with C.