Of course you can start implementing your own thing, but you will waste a lot of precious time reinventing the wheel. Why not take advantage of a validation library that takes care of all this complexity for you?

You can try to build a solution to tackle these issues on your own, but it will cost you time and money... why not use a battle-tested solution to handle all this complexity?

Other frameworks, which use a template syntax built atop HTML — Svelte, Vue, Ractive, Glimmer etc — have historically been fragmented, meaning those tools need to be reinvented many times.

Why not just use that instead of inventing a syntax that's not part of ECMAScript?

Why struggle with custom Syntax DSLs when you can use one so widely supported?

People constantly suggest that I should have just worked with a different library instead of writing another one.

The main rationale for this PR is that, in my hones opinion, Svelte needs a way to support style overrides in an intuitive and close to plain HTML/CSS way. What I regard as intuitive is: Looking at how customizing of styles is being done when applying a typical CSS component framework, and making that possible with Svelte.

Why make another UI component kit when we already got Smelte and SMUI? What's so special about Svelta?

They write their own function because it’s easier and more fun than figuring out how the old function works.