Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why no progress on this POC? #29

Open
jayarjo opened this issue Aug 4, 2019 · 2 comments
Open

Why no progress on this POC? #29

jayarjo opened this issue Aug 4, 2019 · 2 comments

Comments

@jayarjo
Copy link

jayarjo commented Aug 4, 2019

No description provided.

@carloslfu
Copy link

Well, I think this is so complex because with React you have a lot of syntax sugar and ways to handle components dynamically. The reason this approach worked so well with Svelte is that it is built on top of a templating language and that makes the implementation a lot simpler and safer. I'm missing something @Rich-Harris?

@ryansolid
Copy link

It's complicated because React's update model is based on recreating everything. Someone would need to isolate the update path from the create path through static analysis. That being said Hooks probably make this easier. The lynch point comes into deciding how to handle the view logic without just replacing all new DOM nodes every time. This can be handled with clever memoization. It doesn't need to be VDOM level. You can do it in a single pass by storing any conditional values and using a list reconcilliation algorithm similar to what you'd find in a library like lit-html or Svelte.

In any case not sure if this porject is still allive but someone else is trying to take a crack at it here: https://github.com/mohebifar/vidact

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants