truemedian

In that case it might be worth creating a style guide. I'll think about this. Edit: style guide added in b348ad0, any additions and changes are welcome.

I have a few things that float around in my head from time to time, but this covers a lot of the basics. - We should have a **completely unmodified**...

I've started with this in ba42b05, and I agree with using `encode`/`decode` over `stringify`/`parse` as it makes the link between them more obvious

What happens to json depends on if we add a better json implementation in luvi itself (like cjson)

My approach in luvit-bin for ARM binaries is.. not the best, nor would I recommend it. It requires running a full system vm on github's actions machines, which turns a...

I decided to take another stab at this for building just luvi (this can be rather easily extended to both lit and luvit if need be). ARM + OpenSSL binaries...

It's been a while since this has been touched up on, but we can now obtain a run-able (but non-functional) luvi using zig. Building on linux: ```shell $ export CC="zig...

My latest attempt at building luvi. TLDR; I now have luvi building for x86_64-linux-gnu on linux. # Successes - [x] `x86_64-linux-gnu.2.28` (tiny): working luvi, passes all tests - [x] `x86_64-linux-gnu.2.28`...

Seen above, @zhaozg did get cross compiling to work for most of the systems we care about, but I assume thats after modifying the build system to make proper assumptions...

Luvi releases as of 2.9.0 (Feb 19, 2019) no longer provides prebuilt ARM binaries. You will need to build luvi yourself with the steps provided in https://github.com/luvit/luvi#building-from-source, and then you...