▲ | peutetre 8 hours ago | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> But if you’re saying “we need a web thing, how about we use Flutter”… no. If you're making an application, there's really nothing special about the DOM. You might as well control your drawing. That way you don't need to figure out cross browser incompatibilities all day. And here's what someone who used to work on Google Docs has to say about it: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▲ | chrismorgan 7 hours ago | parent [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Please look over my comments on HN about Flutter and pure-canvas and such. There are big problems. There is plenty special about the DOM that you lose and cannot gain back if you go pure-canvas. Links. Scrolling. Text handling. Composition. And various more. Use DOM. Please use DOM. Use canvas for an actual drawing canvas, but for the UI and anything else that’s largely text, use DOM. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|