5 ms·

Zero-cost functional reactive programming for the web

• ranguna 5y ago
  > It does not use VDOM, instead it uses raw DOM nodes for maximum performance. I'm sorry, what? The whole idea of vdom is to increase performance and reduce redundante updates on the actual dom. It's sad to see a project claim that it's fast without showing any actual real world benchmarks.
  • simooooo 5y ago
    Well you’d assume that because it’s reactive you don’t have redundant updates in the first place
  • jpxw 5y ago
    It links to https://rawgit.com/krausest/js-framework-benchmark/master/webdriver-ts-results/table.html https://rawgit.com/krausest/js-framework-benchmark/master/we... in the first line of the README
    • ranguna 5y ago
      Thanks for the link, missed it because "as fast as inferno" is not a synonym to benchmark chart.
  • knubie 5y ago
    This is a common misconception when it comes to the VDOM pattern. See this article for disabusing: https://svelte.dev/blog/virtual-dom-is-pure-overhead https://svelte.dev/blog/virtual-dom-is-pure-overhead
    • ranguna 5y ago
      Good article, thanks!
• ducharmdev 5y ago
  Maybe it's simply my lack of Rust experience, but the HTML builder syntax turns me off to this. I don't want to learn this library's APIs simply to build HTML; at that point I'd rather just manually create and manipulate DocumentFragments - especially since vanilla js still seems more performant according to the linked benchmarks: https://rawgit.com/krausest/js-framework-benchmark/master/webdriver-ts-results/table.html https://rawgit.com/krausest/js-framework-benchmark/master/we...