3 ms·

> I dont think there has been much change in the javascript world in the last few years that hasnt been strictly beneficial. Take a look at Svelte 3. https://

> I dont think there has been much change in the javascript world in the last few years that hasnt been strictly beneficial. Take a look at Svelte 3. https://svelte.dev/blog/svelte-3-rethinking-reactivity https://svelte.dev/blog/svelte-3-rethinking-reactivity

JMTQp8lwXL 7y ago
Two genuine questions. 1. "Svelte is a component framework — like React or Vue — but with an important difference. Traditional frameworks allow you to write declarative state-driven code, but there's a penalty: the browser must do extra work to convert those declarative structures into DOM operations, using techniques like virtual DOM diffing that eat into your frame budget and tax the garbage collector." Is this a practical concern for folks writing CRUD SPAs? I've never experienced degradation in performance due to virtual dom diffing. 2. "Svelte runs at build time, converting your components into highly efficient imperative code that surgically updates the DOM." Angular has its ahead-of-time (AOT) compiler for applications built in production mode. Is this any different from Svelte? It sounds like Svelte claims to be novel, but Angular too does build-time template optimization.
- ng12 7y ago
  I'd love answers to these questions too. Svelte looks cool from a technology perspective but honestly it's biggest selling point is solving problems I don't have.
  - DrOctagon 7y ago
    It isn't about your problems, it is about your user's problems.
    - ng12 7y ago
      Do you think I'm writing web applications for myself?
      - JMTQp8lwXL 7y ago
        I agree with ng12 here. If my users are getting 60FPS+ with Angular or React there is no tangible performance issue my users are suffering from.
  - steve_taylor 7y ago
    It’s solving a performance problem on low-powered, embedded web platforms, such as TVs and even consoles with powerful hardware but inefficient browsers (e.g. PS4’s WebMAF).

JMTQp8lwXL 7y ago

Two genuine questions. 1. "Svelte is a component framework — like React or Vue — but with an important difference. Traditional frameworks allow you to write declarative state-driven code, but there's a penalty: the browser must do extra work to convert those declarative structures into DOM operations, using techniques like virtual DOM diffing that eat into your frame budget and tax the garbage collector." Is this a practical concern for folks writing CRUD SPAs? I've never experienced degradation in performance due to virtual dom diffing. 2. "Svelte runs at build time, converting your components into highly efficient imperative code that surgically updates the DOM." Angular has its ahead-of-time (AOT) compiler for applications built in production mode. Is this any different from Svelte? It sounds like Svelte claims to be novel, but Angular too does build-time template optimization.

ng12 7y ago
I'd love answers to these questions too. Svelte looks cool from a technology perspective but honestly it's biggest selling point is solving problems I don't have.
- DrOctagon 7y ago
  It isn't about your problems, it is about your user's problems.
  - ng12 7y ago
    Do you think I'm writing web applications for myself?
    - JMTQp8lwXL 7y ago
      I agree with ng12 here. If my users are getting 60FPS+ with Angular or React there is no tangible performance issue my users are suffering from.
- steve_taylor 7y ago
  It’s solving a performance problem on low-powered, embedded web platforms, such as TVs and even consoles with powerful hardware but inefficient browsers (e.g. PS4’s WebMAF).