one of the things I liked about Special K was the "swizzler" syntax it borrowed from GLSL. Hard to generalize with the same level of concision, though

@ktye have you tried ngn's js k from iphone/android?

didn't seem like the split editor is making much difference, but could be an iphone issue of course.

@JeromeIbanes no, only with desktop browser

could it be due to an iphone setting perhaps?

I mean security "feature"

@JeromeIbanes maybe. if nk.html works, that could be because of the server.

@JeromeIbanes i added an "editor+output" view, as an alternative to the repl

ctrl+enter executes the code in the left pane (as if it's in a file) and shows output in the right

maybe it needs emojis

does anyone have ideas for a compression algorithm for permalinks?

@ngn how large is your bytecode compared to src?

@ktye the wasm is 97kB, the source (?.c and ?.h) is 70kB

@ngn i mean k-bytecode

ah. no idea.

mayebe not shorter than src (for url)

it's hard to measure. does it include headers and the free space after arrays? how are constants counted? symbols?

should the bytecode of internal k-strings be counted too?

and why does it matter anyway

@ktye some information is lost when compiling

e.g. a[b] and a b and a b compile to the same bytecode

@ngn can you format(uncompile) byte code?

no

i was thinking, the first step could be replacing base64 with base81

there are 81 chars that are valid in a url "fragment" (the part after #)

that should be an improvement of ~5% (log(81)/log(64))

@ngn or escape # % ^ [ ] { } \ " < >

@ktye but escaping is very expensive

@ngn remap to upperspace first

3 bytes for 1 char

why 3 bytes, you can do your own quoting.

true