wefx VS pp

I'm particularly curious on what parts cheerp adds to their clang+llvm base. Presumably it's something like the C standard target library for WASM/JS?

For reference, here's examples of what you could do with the baseline clang with wasm (but not JS?) [1] [2] [3], referenced from a similar thread on HN.

[1] https://github.com/ern0/howto-wasm-minimal

[2] https://github.com/robrohan/wefx

[3] https://github.com/PetterS/clang-wasm

I've used a similar pipeline to create "books for code and infrastructure". A/k/a coding in a somewhat literate programming style. Similar to what is described here:

gemini://gemini.robrohan.com/2022-04-23-narrative-programming.md

With output that looks similar to this: https://github.com/robrohan/wefx/blob/main/docs/manual.pdf

Using a github action like this: https://github.com/robrohan/wefx/blob/main/.github/workflows...

(most of the code borrowed from those projects)

You can do it with just plain markdown files and use directories for chapters / organization if you're just going for prose.

I've thought about using the process to try to make open textbooks where you can mix and match chapters, but I don't have any experience in that field.

Anyway, can confirm, it's an incredibly useful process.

Not trying to steal your thunder, but here is another nostdlib clang -> wasm example with malloc, a few math functions, rand, and writing to a canvas doing animation.

=> https://github.com/robrohan/wefx

I haven’t seen this version mentioned in the thread - if you don’t need a lot of precision, here is a simple 4 line version[1] and here’s how it works[2].

Not sure who initially came up with it.

[1] https://github.com/robrohan/wefx/blob/1a918cc2d5ad87402a3830...

[2] https://www.desmos.com/calculator/lo7cf60mjz

Talking about the downsides of Markdown: it's not that you can't use Markdown without tables. Since there is not just one Markdown flavor, there are variants such as this one which do define table support and more. This introduces other difficulties to users of Markdown. For example, you need to know what kind of Markdown is supported with your current tool-set. In my business life, we do use a tool-chain to generate documents via Markdown, pandoc and pp (I'm not sure if the correct link is this or that). Using that, I may use even two different kinds of Markdown tables with different syntax and different features for formatting. I guess I don't need to explain much more on that to emphasize that this is a complicated thing to write and maintain since editing tools do not seem to support Markdown tables at all or they only support only one kind of Markdown table and not all of them. It's a big mess that the original authors or Markdown could not foresee and later, nobody could fix it so far although there is CommonMark which tried to fix it but it didn't stick much.