it's a hard problem, because when Google cares it might not be good for users of the various projects/tools/languages. these projects has specific goals (that s

it's a hard problem, because when Google cares it might not be good for users of the various projects/tools/languages. these projects has specific goals (that serve Google's high-level goals in various ways) and circumstances (which many times lead to significantly different engineering trade-offs). Google starts projects with a lot of initial investment (new language/compiler/toolset/SDK/std-lib/frontend-component-library), but then their boldness almost disappears, and it takes a lot of time for them to finally catch-up, and on top of that they usually take a long time to "care" about things important for users (non-google developers). for their care/support/long-term-commitment to matter, first they (would) need to position themselves as downstream users of Flutter, and for that they first need to transform leadership into a community-driven something.