Show HN: Percy – A Rust and WebAssembly isomorphic virtual DOM implementation
1–10 of 53 posts
Re: Show HN: Percy – A Rust and WebAssembly isomorphic virtual DOM implementation
#2can you write an app in just once file and mark what can run in the client and what must only run on the server?
Re: Show HN: Percy – A Rust and WebAssembly isomorphic virtual DOM implementation
#3Hi chinedufn, this looks very interesting. I am at the same stage as you re. "I REALLY want to use this for everything ...".
I see you're using wasm_bindgen quite a bit, but from a cursory look at the code; I can't figure out something:
I can see how you're using wasm in the front-end, but could you please elaborate a bit more about in the backend? I presume that your backend is Rust based?
I spent last weekend porting some code from NodeJS to a wasm module. I got it sort of working on Node, but haven't tried it on the browser yet (ran out of weekend).
I'm quite optimistic about wasm [and Rust with wasm_bindgen]. I'd been thinking of writing a native add-on for Node, but the idea that I can use wasm instead is exciting.
Re: Show HN: Percy – A Rust and WebAssembly isomorphic virtual DOM implementation
#4Can someone ELI5(+) what an isomorphic virtual dom is?
Re: Show HN: Percy – A Rust and WebAssembly isomorphic virtual DOM implementation
#5Can someone ELI5(+) what an isomorphic virtual dom is?
An isomorphic virtual DOM is much like an inverted-index homomorphic shadow DOM, but instead of using a shadowed mapping they virtualize the original elements themselves.
Re: Show HN: Percy – A Rust and WebAssembly isomorphic virtual DOM implementation
#6Can someone ELI5(+) what an isomorphic virtual dom is?
An isomorphic virtual DOM is much like an inverted-index homomorphic shadow DOM, but instead of using a shadowed mapping they virtualize the original elements themselves .
> An isomorphic virtual DOM is much like an inverted-index homomorphic shadow DOM, but instead of using a shadowed mapping they virtualize the original elements themselves.
Not sure if this is ironic, but a 5 year old definitely wouldn't understand this!
Re: Show HN: Percy – A Rust and WebAssembly isomorphic virtual DOM implementation
#7Can someone ELI5(+) what an isomorphic virtual dom is?
An isomorphic virtual DOM is much like an inverted-index homomorphic shadow DOM, but instead of using a shadowed mapping they virtualize the original elements themselves .
I'm not sure if you are you are fucking with me or if i'm just ery stupid.... :(
Re: Show HN: Percy – A Rust and WebAssembly isomorphic virtual DOM implementation
#8Can someone ELI5(+) what an isomorphic virtual dom is?
An isomorphic virtual DOM is much like an inverted-index homomorphic shadow DOM, but instead of using a shadowed mapping they virtualize the original elements themselves .
Can someone ELI5 what an inverted-index homomorphic shadow DOM is? TIA
Re: Show HN: Percy – A Rust and WebAssembly isomorphic virtual DOM implementation
#9Can someone ELI5(+) what an isomorphic virtual dom is?
An isomorphic virtual DOM is much like an inverted-index homomorphic shadow DOM, but instead of using a shadowed mapping they virtualize the original elements themselves .
I think they asked for an ELI5 not an ELIPhD. :P
I don't think many would understand what an inverted-index homomorphic shadow DOM is, though I think I can cobble together a very very vague understanding.
Re: Show HN: Percy – A Rust and WebAssembly isomorphic virtual DOM implementation
#10Can someone ELI5(+) what an isomorphic virtual dom is?
Sorry for the confusion I tried to write a title that would fit and guess I missed the mark!
What I really mean is a virtual dom implementation that
- On the frontend can diff/patch a real DOM node - On the backend can render into an HTML string that you can serve
So my intended takeaway with that title was:
-> A virtual dom implementation that allows you to write frontend web applications that support server side rendering.
Apologies for the buzz-wordification I didn't even realize ha!