I’m sorry but you seem to have misunderstood the request for a separate stdlib. Size is only a small part of it. I didn’t realise this until now, but your summary issue about it missed one of the original issues:
This issue very clearly states the reason I and others have requested this for years now. We want to publish compiled JS libraries from ReScript that depend on just the stdlib JS files. It is nice that
bs-platform no longer compiles OCaml, but there’s still over a hundred megabytes of things that are not relevant to a library published in this way.
So yes size matters but there are plenty of other factors that matter for projects where the
node_modules folder needs to be published; of the top of my head I can think of security as a big one, uploading unnecessary binaries is never a good idea, and bandwidth / hosting costs are another. In Javier’s specific example creating a vscode extension means the binaries must be uploaded to Microsoft, who might have a problem with it if the extension becomes popular while including a hundred megabytes of stuff that isn’t used.
I will admit the vast majority of ReScript users today don’t need this. They’re building ReScript applications or libraries designed to integrate into ReScript applications. However in terms of the wider JS community that is quite limiting, and I think being able to publish a library for JS users without depending on the full
bs-platform is a good goal to have.