4 ms·
qwik may be appealing technically, but it's not the best fit for web applications because: 1. You're required to use qwik's API for React, limiting your flexib
by nazka 4y ago
qwik may be appealing technically, but it's not the best fit for web applications because:
1. You're required to use qwik's API for React, limiting your flexibility and hiring.
2. The lack of compatibility with the vast React components and libraries ecosystem means you'll have to start from scratch on all your components, even essential ones like calendars, MaterialUI, charts, etc...
If your focus is on creating a website and try something else than say Gatsby, then qwik may be a good option. However, for web applications and the ability to fully utilize the React ecosystem, it doesn't seem to be the best choice.
- mixedCase 4y agoPoint 1 is irrelevant unless you're hiring devs who cannot adapt quickly to minor changes, in which case it's an useful hiring filter. Everything else about not being able to integrate with the React ecosystem is incorrect, please read this part of the documentation where it explains in detail how to do it and how to integrate it with Resumability in mind: https://qwik.builder.io/integrations/integration/react/ https://qwik.builder.io/integrations/integration/react/
- nazka 4y agoMy bad, sorry for the misinformation from my previous comment. I will dive more into the link you gave me to see the limitations they talk about and the small vs big island. But it makes me reconsider using qwik for future projects. Thank you for point this out to me and taking the time to respond!