4 Matching Annotations
  1. Oct 2020
    1. Tree-shaking is the process of analyzing the code files that are required to run your application and then including only code that is actually used by your application.
  2. Sep 2020
    1. Svelte started with no decoupling anywhere, with everything available at compile-time. Then <:Component> introduced separation at the component level -- but they're still coupled at properties. The spread feature would fill that gap. I see it as an intentional separation as opposed to an accidental shot at static analysis.
    1. The static analysis considerations make things like hero.enemies.map(...) a non-starter — the reason Svelte is able to beat most frameworks in benchmarks is that the compiler has a deep understanding of a component's structure, which becomes impossible when you allow constructs like that.