The 'Mustaches' bit killed it for me, but up until then I was enjoying the simplicity of the API. I like React (and React-like implementations) because of being able to use JS to build up a view
Yep. For me React JSX simplifies component building.
Svelte – A UI framework that compiles into tiny standalone JavaScript modules
31–40 of 236 posts
Re: Svelte – A UI framework that compiles into tiny standalone JavaScript modules
#32Isn't the problem of including only the code the component actually needs already solved with dead code elimination? So the framework authors can include new features but as long as your component doesn't use them the code for those feature does not end up in the final bundle you serve to the user.
I sure am missing something here because the author of Svelte is actually also the author of rollup.js [1] which does exactly that, it eliminates dead code via its tree-shaking mechanism.
[1]: http://rollupjs.org
Re: Svelte – A UI framework that compiles into tiny standalone JavaScript modules
#33Mores like Sass for JS. exactly what we need!
Re: Svelte – A UI framework that compiles into tiny standalone JavaScript modules
#34Love it. I think the most discussion-worthy quote I found in the docs is this: > It's currently fashionable to avoid two-way binding on the grounds that it creates all sorts of hard-to-debug problems and slows your application down, and that a one-way top-down data flow is 'easier to reason about'. This is in fact high grade nonsense. It's true that two-way binding done badly has all sorts of issues, and that very la…
Redux fixes two way binding by forcing the developer to emulate it using such a convoluted mechanism that there's no way to see that it's still broken; great job, FB rockstars!
Re: Svelte – A UI framework that compiles into tiny standalone JavaScript modules
#35Earlier quoted context omitted.
Trying to avoid boilerplate is in my experience not about laziness - especially when you consider the extreme lengths a lot of developers will go to to eliminate duplication and boilerplate from their codebases. Copying a Redux reducer that implements a standard set of CRUD actions is lazier in my mind than trying to abstract common patterns away. For me at least, the reason boilerplate bothers me so much is that it…
"the reason boilerplate bothers me so much is that it impacts the readability of my code" But if you hide boilerplate you not really improve readability. Not seeing what is really happening just creates the illusion of readability.
Taken to its extreme, that argues for writing everything in assembly language.
React's virtual DOM diffing makes components more readable than the previous style of writing code to explicitly manipulate the DOM and totally hides what's really happening. However, we trust that it's going to do the right thing, just as we trust that the JavaScript engine will do the right thing when it JITs and interprets our code.
Re: Svelte – A UI framework that compiles into tiny standalone JavaScript modules
#36Love it. I think the most discussion-worthy quote I found in the docs is this: > It's currently fashionable to avoid two-way binding on the grounds that it creates all sorts of hard-to-debug problems and slows your application down, and that a one-way top-down data flow is 'easier to reason about'. This is in fact high grade nonsense. It's true that two-way binding done badly has all sorts of issues, and that very la…
Redux fixes two way binding by forcing the developer to emulate it using such a convoluted mechanism that there's no way to see that it's still broken; great job, FB rockstars!
Redux is to manage state across the app.
Re: Svelte – A UI framework that compiles into tiny standalone JavaScript modules
#37The 'Mustaches' bit killed it for me, but up until then I was enjoying the simplicity of the API. I like React (and React-like implementations) because of being able to use JS to build up a view
Yeah, same. Can't give up JS/TS templating and typesafety.
simply for a smaller size, I already use something that is way, way smaller than react.
Re: Svelte – A UI framework that compiles into tiny standalone JavaScript modules
#38React fanboy chiming in to say... an interesting approach to what is probably a problem.
i wonder, though, if compilation is really better than creating a library? if we look at the REPL output [0], we can see what comprises the bones of a Svelte component, and how much generated code will be replicated.
it also shows that the more interesting part here is it's method for rendering. it's use of data binding and compilation means we don't really need something like VDOM to stay efficient (at least, not a VDOM running in the browser).
[0] https://svelte.technology/repl/?gist=0ed5146aa22c28410dfcff2...
Re: Svelte – A UI framework that compiles into tiny standalone JavaScript modules
#39So this is like GWT, minus Java? GWT's treeshaker removes dead code and outputs fat-free plain JS.
Re: Svelte – A UI framework that compiles into tiny standalone JavaScript modules
#40That seems quite amazing, especially the todo example being over 10 times smaller than the React one. Are there any drawbacks to this approach?