Kat Marchán

Same reason `anyhow::Error` doesn't implement it: the blanket impl in std for `impl From for T`

I'll have to think about this one for a bit: it's a pretty significant API breakage, and I'm trying to limit things that change the API this significantly. The only...

Yeah there's a certain extent to which, considering how widely used Miette is, it needs to be "mostly done", and we don't really have the ability to make major changes...

The tests are relevant. If I recall, we only started doing things without `--all-features` because of some now-forgotten reason that was preventing them from working on CI in particular.

How about something like this, where we focus on getting teams up and running and functional as quickly as possible, with the bells and whistles handled more granularly by separate...

I'm personally against adding shared-memory threading to Node. I think having stuff like lightweight WebWorkers is pretty alright, and probably requires a lot less work -- but the implications on...

I'm pretty onboard with some sort of native WebWorker thing being added. Those could actually be super handy, and they're shared-nothing so 💯

As a former fibers user, I too believe that async/await has essentially supplanted fibers: and async/await has the advantage that it does not need additional VM-level work from the project,...

@ngot oof. Those benchmarks are against v0.10. You might wanna update this to compare against the latest `master`. That is an ancient node by current standards, not even counting Turbofan,...

This is really cool -- to ask my next question: do you think it's possible to merge the two such that fibers are the underlying implementation structure for async/await, so...