domdiff VS petite-vue

> There are lighter-weight shadow dom frameworks out there (than Vue/React/Angular) so why would you want to write one yourself?

You can even avoid a shadow DOM entirely:

https://github.com/WebReflection/domdiff

https://github.com/WebReflection/uhtml

If by faster you mean faster than React I think there is evidence it can be. The author of the issue writes lots of dom utility and rendering libraries and I believe domdiff is more or less what he describes in the post:

https://github.com/WebReflection/domdiff

You can find it placed way above React in the usual JS rendering benchmarks:

https://rawgit.com/krausest/js-framework-benchmark/master/we...

Now it's not entirely clear whether these benchmarks convey something meaningful except for maybe the point that most frameworks are quite fast. That being said I think it's developer experience that really stands to improve. Thinking of view as a pure function of state was a great innovation, but existing implementations can end up fracturing the view into virtual doms and non-virtual. Then you end up with problems like D3 and React not coexisting.

I feel like I heard something from the lit-html folks that a long term aspiration was to integrate some learnings from the project into chrome, but I haven't been able to find where again.

There has been a trend in JS with libraries becoming idiomatic to the language to later have the issues they targeted be addressed natively (a la JQuery).

In general, I definitely appreciate your point about adding complexity to the platform, but I think when it comes to web technologies that ship has long sailed. I really see it as an opportunity to bring a lot of simplicity, chiefly filling that void that's birthed a billion JS frameworks.

Thanks for the thoughtful comment.

Something similar: https://github.com/vuejs/petite-vue (6kb subset of Vue) but the project seems abandoned.

I started with petite-vue because Vue seemed too large of a file size for my simple projects. Wanting to use Vue but after reading some of the comments, I might go with Svelte.

Like: petite-vue And/or a zero-dependency lightweight state management solution.

I recommend trying https://github.com/vuejs/petite-vue as a minimalist library for declarative reactive view/model data binding, it could at least halve the code used for generating view

Maybe I’ve spent 5 days on and off researching this. I was able to recreate it perfectly using petite-vue https://github.com/vuejs/petite-vue which is nice, but it does not have all the features I need in Vue3

“petite-vue is indeed intended to fill the gap for progressive enhancement cases where Vue 3 would be too heavy-handed.

It is not abandoned, but rather it is considered "done" because the scope is well defined. I don't think it needs more features (as that would defeat the purpose of being lean and minimal). If you find yourself needing more than what petite-vue provides, you can either go up to Vue proper, or try https://alpinejs.dev/.

That said, I should update the README to indicate this more clearly.”

Github discussion: https://github.com/vuejs/petite-vue/discussions/53

You might consider doing as much as possible in Razor pages and then use https://github.com/vuejs/petite-vue for any functionality you might (components/interactivity/etc.) need.

As another alternative, you could look at petite-vue if you just want to sprinkle from Vue-like components throughout your site... Doesn't have the full force of vue, but maybe it's enough.