Post

This is super fascinating! I'm wondering if Porffor is dependent on a direct interface between browsers and WASM? Can't find that proposal, but I know the idea has been around for a while. Will Porffor still need to generate JS bindings to communicate with the DOM? I'd love to look at the perf diffs

I'd love to see some benchmarks on compiled JS with Porforr. When compared to JIT implementations for example. Is Porforr able to outperform, or is the main goal rather to be able to provide native CLI and use JS without a runtime? Do you use the Typescript types to try to infer and optimize data?

Do you see Proxy ever being supported by Porffor? Alternatively, are there features that you think Porffor will never support?

My no1 recommendation is to plan ahead for instrumentation libraries. A lot of people want it and it's a huge pain to get right if it is an afterthought. I am mentioning this because instrumentation libraries abuse dynamic import.