![]() Flutter delegates down to Android or iOS's implementation of these features, and as we were neither, we had no such thing. Chromium has a pretty decent accelerated rendering stack, and boatloads of work went into getting it optimized for smaller SoC type devices (work often done by friends / coworkers of mine, actually).Īnd switching to Flutter meant having to jerry-rig (or worse, rewrite from scratch) basic things like accessibility (screen reader, magnification, etc.) or virtual keyboard that Chrome (or at least ChromeOS) had solutions for and we had just spent over a year making work for our product. V8 and the Chromium rendering engine have (low estimate) hundreds of thousands of hu-man hours of optimization put into them. One promise was that it would be faster (because "native"), but this was frankly based on a lot of untested assumptions and biases and was never correct. To me this was classic Joel Spolsky "Things You Should Never Do, Part I" aka "rewrites considered harmful" alarm bells, but who listens to me, I'm just a grouchy old engineer. not web or android or ios target), and only a few months after said product launched. Slowly and tortuously, rewritten from a JS/HTML application to Dart/Flutter on "native" (i.e. I saw it happen in two PAs, and the second time it involved literally rewriting an entire shipped product on a platform I worked on. IMHO that's what happened with Dart & Flutter. Often it comes down to certain engineers having outsized voice and influence combined with them having a preferred hammer and then hunting around the organization looking for nails. Honestly, as an ex-Googler (10 years), I have to say it's never that simple to explain why some tech is adopted or pushed at Google and it's never so top-down and unicausal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |