Byte representation

[GregTheGreek]

Related to #35
Is your feature request related to a problem? Please describe.
We are somewhat restricted in regards to what we can do with bytes.

Describe the solution you'd like
Ideally something native to vanilla JS, C/C++ bridge or WASM.

Describe alternatives you've considered
Webpack so we can use class Buffer() from node. Not ideal.

[aunyks]

Is this for individual bytes or byte arrays? If the latter, why isn't Buffer ideal?

[GregTheGreek]

We're updating our contributers and "mission statement" so to speak. Our ideal goal is to not use node, so we can maintain browser support. Without using webpack/browserify/et al

[aunyks]

Uint8Array is a great runtime-agnostic representation of bytes imo.

Although I must ask: how is networking planned to take place without assuming Node as the target runtime and then browserifying for the browser? Is there an isomorphic TCP library? Basically I'm asking how p2p stuff is gonna go down in the browser.

[GregTheGreek]

You make a good point, maybe I should clarify. The goal is to use it as little as possible. I think we can get away with a TCP library, we had someone make a poc for a wallet app, not sure how extensive it is though...

[ansermino]

Can you please elaborate on this? What are you trying to do with bytes and can't?

[GregTheGreek]

This is outdated tbh. Bytes 8array put us in the right direction

[ansermino]

Does that mean we can close this?

[wemeetagain]

not related to just this issue but:

I believe we're going to need to use a bundler of some sort, regardless if we use Buffer or not, to run this software on the web.
Web JS can't just simply import x from y nor can it require(z) without being linked together beforehand.

[GregTheGreek]

Mmm, this is true with plain HTML. Best case scenario is meant for react, angular etc... That way we can get away without it.