Tim Caswell

@diasdavid I don't think you need to know the type, just make it part of the storage format where the payload is arbitrary. ``` pointers* data ``` Though this does...

@kemitchell I don't think this is what you meant, but you gave me a great idea. What if the storage engine decoupled storing *data* with setting the *key* for that...

Looking back at the top post, I don't think this idea provides all the benefits. Having the storage engine be able to assume it's content addressable really enables all kinds...

I like the rename idea. It's lower level so a little harder to use, but it reduces the complexity of the browser implementation a lot (compared to CAS built-in). Then...

FWIW, I recently updated my luv bindings to use the latest libuv code. Feel free to look at my code for ideas. Yes scandir is tricky. For my bindings, I...

I want luvit/web to be as portable as possible. But I don't think I can get away from having a defined spec for readable and writable streams as well as...

For data encoding, we could add encoding arguments to both :read(encoding) and :write(chunk, encoding) to allow supporting multiple data types. :write could probably even auto-detect the type and convert for...

@indutny, would you have time / interest to see if JIT can be added without compromising the main goals? I seem to remember [candor-lang](https://github.com/indutny/candor) was fairly simple.

@svaarala what about a tracing jit like luajit instead of the inline-cache and hidden class style of V8? Is JS code just not suitable to this kind of optimization?

Right, I don't think a luajit style jit would work well for the way most people tend to write JS code with tons of property lookups. When I'm writing luajit...