After a little more poking around here's how we can compile the emitted C from JavaScript to an executable. JavaScript to C ./build_release/bin/shermes -emit-c -O -g -v permutations.js C to executable /usr/bin/cc permutations.c -O3 -I./build_release/lib/config -I./hermes-static_h/include -DNDEBUG -g -fno-strict-aliasing -fno-strict-overflow -L./build_release/lib -L./build_release/jsi -L./build_release/tools/shermes -lshermes_console -Wl,-rpath ./build_release/lib -Wl,-rpath ./build_release/jsi -Wl,-rpath ./build_release/tools/shermes -lm -lhermesvm -o permutations More on reddit.com

I'm developing a small open-source javascript library, and I was wondering about the proper method for compiling the source into one javascript file. It's easier to develop if the code is split into More on softwareengineering.stackexchange.com

This is closed source?

More on reddit.com

I'll do what I can about things I know about, others might know more. TypeScript, as you mentioned, dominates. This is both because it's got a wonderfully expressive and ergonomic type system, and because it's somehow still just a very thin layer over JS - "compilation" basically just amounts to stripping away the types - meaning it integrated smoothly into existing codebases. The amount of work and cleverness that's gone into it - both engineering work and also socially - is gargantuan. That said, you're right: it provides a pleasant enough development experience for a wide-enough range of developers that it's sucked a lot of air out of the room and killed a lot of enthusiasm for alternative languages. Elm I don't know a ton about engineering-wise. People who like it like it quite a bit. I think it's roughly something like a simpler, more user-friendly Haskell-esque language wedded to a Redux-ish state management system, but I could be wildly off-base here. What I do know is that the creator is known to be somewhat dictatorial, and this has alienated some segments of the community a bit. The language seems to be dead or dying; the creator isn't really working much on it (most recent release was nearly five years ago, in 2019) and isn't really welcoming contributions. ReasonML (and ReScript) started as an Ocaml -> JS compiler, wedded to a new surface syntax for Ocaml. Since then a contingent of people wanted to make it diverge more from Ocaml and integrate more tightly into the JS ecosystem, and broke that out into ReScript. Meanwhile ReasonML trucks along. In theory I can imagine that ReasonML could be a real powerhouse of a language - you could write code in one very powerful and expressive language that works on the frontend, the backend, and could be compiled for WASM. Unfortunately the tooling and libraries to make that happen (and happen in a friendly way) aren't here yet and, knowing the Ocaml community, sadly probably never will. If I'm being honest: I use ReasonML professionally and I kind of hate it. I don't like the syntax even as much as Ocaml's, and while stronger type safety is very nice I mostly just miss the conveniences of TypeScript. PureScript is a better Haskell on a number of dimensions that compiles to JS. I'm very sad that there doesn't seem to be a good native compiler for it, because frankly I'd rather use it than Haskell. Development seems to be slow but still on-going. I'd love to have a reason for using this but frankly TypeScript is "good enough"; I suspect I'd come to resent it as I have ReasonML. More on reddit.com