emscripten

> Malloc and memory allocation methods are at least 10k+ lines of code for instance. Only the really big ones, e.g. here is Emscripten's allocator that focuses on small binary size and is implemented in about 1.5 kloc (ignoring comments and whitespace it's actually under 1 kloc), and that allocator is perfectly fine for most use cases (especially C code bases which typically don't have a high allocation frequency): https://github.com/emscripten-core/emscripten/blob/main/syst... ...and Seb Aaltonen's offset allocator (used for allocating GPU buffers in his Vulkan API wrapper) has under 500 lines of code: https://github.com/sebbbi/OffsetAllocator/blob/main/offsetAl... Right tool for the job etc... big general-purpose allocators like jemalloc or mimalloc are usually a bandaid to somewhat salvage a failed memory management strategy.

Is node::vfs the new solution for JupyterLite filesystems? From https://github.com/jupyterlite/jupyterlite/issues/949#issuec... : > Ideally, the virtual filesystem of JupyterLite would be shared with the one from the virtual terminal. emscripten-core/emscripten > "New File System Implementation": https://github.com/emscripten-core/emscripten/issues/15041#i... : > [ BrowserFS, isomorphic-git/lightningfs, ] pyodide/pyodide: "Native file system API" #738: https://github.com/pyodide/pyodide/issues/738 re: [Chrome,] Filesystem API : > jupyterlab-git [should work with the same VFS as Jupyter kernels and Terminals] pyodide/pyodide: "ENH Add API for mounting native file system" #2987: https://github.com/pyodide/pyodide/pull/2987

> The cost of turning written business logic into code has dropped to zero Then go and throw your $0 to fix some real bugs on GitHub.. really, if AI works so well, why are all those issues still open? Look, almost 2K issues open here: https://github.com/emscripten-core/emscripten/issues If AI really works like non-technical people think it does, why doesn't Google just throw their AI tool to fix them all?