Flutter requires web devs to throw out their JavaScript investment and their web support is not viable for Progressive Web Apps.
I think it enhances their productivity without sacrificing their knowledge in JavaScript, I think most dev switch to flutter suffers from the web dev environment(tooling is not efficient, spend less time in configuration and start coding). Also, flutter supports PWA.
Flutter might support PWA, but it's not PWA ready. The amount of JS required for Flutter Web is astronomical as they have to implement browser primitives like text selection and copy/paste from scratch. Their own official gallery demo ships a 4MB JS file! I don't consider that a viable option for PWAs which, according to Chrome and web perf leaders, should be in the single digit KB or low double digits and with much better lighthouse scores. Contrast that with the innovation happening in the rest of the PWA ecosystem resulting in tiny bundles and incredibly high performance web apps and PWAs.
I think the gallery demo ships with static assets(and not lazily loaded through CDN) that's why it ships 4MB and webp image is not supported. Flutter for web is not entirely ready for production, like SEO for example. Text selection is supported from another widget(SelectableText()). I still think PWA is still pre-mature.
Overall. I generally don't use flutter for web in production. But I really like its support from other online editor(codepen for example)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think it enhances their productivity without sacrificing their knowledge in JavaScript, I think most dev switch to flutter suffers from the web dev environment(tooling is not efficient, spend less time in configuration and start coding). Also, flutter supports PWA.
Flutter might support PWA, but it's not PWA ready. The amount of JS required for Flutter Web is astronomical as they have to implement browser primitives like text selection and copy/paste from scratch. Their own official gallery demo ships a 4MB JS file! I don't consider that a viable option for PWAs which, according to Chrome and web perf leaders, should be in the single digit KB or low double digits and with much better lighthouse scores. Contrast that with the innovation happening in the rest of the PWA ecosystem resulting in tiny bundles and incredibly high performance web apps and PWAs.
I think the gallery demo ships with static assets(and not lazily loaded through CDN) that's why it ships 4MB and webp image is not supported. Flutter for web is not entirely ready for production, like SEO for example. Text selection is supported from another widget(
SelectableText()). I still think PWA is still pre-mature.Overall. I generally don't use flutter for web in production. But I really like its support from other online editor(codepen for example)