4 ms·
It's more to keep scope small until we feel confident about the experience. Theoretically, we can scale to other declarative frameworks, but we'd have to imple
by hoakiet98 1y ago
It's more to keep scope small until we feel confident about the experience.
Theoretically, we can scale to other declarative frameworks, but we'd have to implement a parser for each. We're sticking with React/Next for now since that is the majority of use cases with plans of supporting other frameworks when the experience feels good enough.
There's a comment under about Svelte support as well (which is what the initial prototype supported) and I gave a similar answer there.
https://news.ycombinator.com/item?id=44127653 https://news.ycombinator.com/item?id=44127653
- dennisy 1y agoYeah I saw that comment. Maybe this is just a naive opinion it I do not get why you must target a framework at all VS just pure CSS/HTML and later allow people to convert into their framework. I feel that at the design stage a framework should not be discussed, since that is an implementation detail.