Paul Miller

I have a big problem with Buffers. 1. `buffer.slice()` is mutable copy, `uint8array.slice()` is immutable. This is very bad. Recently got hit with a bug report. I was checking for...

> Examples where Buffer may be needed: > The API needs to work with hex or base64 encoded data. That needs to be implemented as a hex/base64 decoder in stdlib,...

The alert is false, report this to GitHub: https://github.com/github/advisory-database/pull/531

Hey folks, this is very important: basically Parcel cannot use modules which support both common.js and ESM. We're forced to revert and drop support for ESM because of that.

@Daninet cc

Would be great to have this merged! Filippo doesn't seem to work on age much, so I think it's fine to make `rage` different in some regards.

Yeah, STREAM seems to be the slowest part here. Multicore optimizations should also speed-up things massively. See [the gist](https://gist.github.com/paulmillr/101bd4ecd8644ff2689f2e18571797b7) for a tiny & very performant example of Rust threads.

Could be great to understand what exactly slows us down at this point. Not sure what is the best way to profile traces in Rust.

>rage compiled with AVX2 is 2.66x slower than age. Is there any reason to *not* compile with AVX2? I think, almost every x86 cpu nowadays supports it?

@tarcieri i've thought a nonce-misuse-resistant construction cannot be 1-pass? Specifically, SIV. Am I wrong?