Skip to content

Conversation

@paoloricciuti
Copy link
Contributor

@paoloricciuti paoloricciuti commented Oct 29, 2025

Pushing this already (obviously it's not finished at all) because since it's a bit of a weird one I think it's important to get feedback immediately to not rewrite everything in case it's not the direction we want to go towards.

RENDERED VERSION

Copy link
Member

@marcoow marcoow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think when talking about the why you need to talk about the what as well which for example could cover the fact that Svelte scales nicely from widgets to large-scale apps (and maybe native via Lynx eventually)


{% endnote %}

## Compiler
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd be more explicit here about the fact that this results in potentially better long-term maintainability: the compiler acts as a buffer between Svelte and the platform so that Svelte code doesn't need to change when the platform changes or develops further -> better long-term maintainability and more long-term safety for investments into Svelte

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this basically the third point?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's implied in your 3rd point but not explicit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants