| > For people coming from traditional web development, I find that Svelte is the most comfortable tool for them to learn. That's a helpful endorsement, thank you. I'd found Svelte, and it did look promising and more comfortable. > I would not describe it as a simpler model however - you're effectively writing two applications that communicate together to make one. The benefits you get for that are beyond worth it in my opinion. > I don't know if I would be able to do very well explaining it myself, but generally - it allows for a more clean separation between systems. My backend exposes an API that my frontend can communicate with over background HTTP requests. That's a much better explanation than anything I'd seen before. Every description I'd seen before holds up React and Vue as simpler or easier than traditional web development, and that didn't seem at all accurate. The potential architectural advantage, at a cost of simplicity, makes much more sense. (I do rather like statically compiled type-safe templates, but at that point, that's a separate question of preferred development language.) > - Component structure is just better to work with than template structure (expanded upon below) That's one of the clearest advantages I've previously recognized. The idea of putting the HTML and CSS and JavaScript for a component in one place, and combining that with other components, makes perfect sense to me. |