Sam

Working. I didn't dare dream that I'd be able to jailbreak my fancy-ass TV and run RetroArch on it. Thank you, heroes! ``` "hardware_id": "HE_DTV_W21O_AFABATAA", "product_id": "OLED48C17LB", "core_os_release": "6.2.0-27", "webos_manufacturing_version":...

@Pauan yeah, absolutely. The initial ideas I have around `ObjectProps` are somewhat nascent, but as you've rightly pointed out, querying data out of ad-hoc objects from Rust-side is a little...

@Aloso another great point you had is being able to augment properties onto existing Objects. If we opted to not go for the macro approach and stick with the existing...

> I think there's a pretty simple solution: the build() method would return Result, and then a new unwrap_build() method is added which calls unwrap_throw(): Are you getting `ObjectProps` mixed...

Thanks for the feedback @RReverser - what you're working on sounds very interesting and I'll be sure to check it out when you put some code up > Either way,...

Of course performance is an important aspect here, but when I think about this more I think the main purpose of `ObjectBuilder` would be to provide better ergonomics for the...

I have a habit of being kinda verbose when I'm trying to get a point across. Let me try and distill it into a much easier TL;DR: I think that...

> Unfortunately not, you still need to copy the memory from JS to WASM or the other way around. Not strictly true, see [`TypedArray::view`](https://rustwasm.github.io/wasm-bindgen/api/js_sys/struct.Uint8Array.html#method.view). You can take any arbitrary block...

Okay so I wrote an entirely unscientific set of benchmarks to test the overhead of building a simple `{"foo": "bar"}` object. Here's the code: ## lib.rs ```rust use js_sys::*; use...

Okay slight addendum. I knew something felt a little weird about the results I saw seeing. I was compiling the crate in development mode. Heh. Results in releasemode: Test |...