that android project of some months was a venture into flutter (and haven’t touched it before)

I had similar impressions on some things, and mixed on other

dart’s a moderately good language with some nice primitive, tooling overall is pretty mature, broad strokes works well for variant targeting and shit

libraries though holy shit the current situation (then) was a mess. one minor flutter sdk upgrade and a whole bunch of things just exploded (serialisation things in nosql-type libraries I tried to use for the ostensible desired magic factor (just went back to sqlite stuff again after)). this can’t have been due to sdk drift alone, and felt like an iceberg problem

and then the documentation: fucking awful, for starting. excellent as technical documentation once you grok shit but before that all the examples and things are terrible. lots of extremely important details hidden in single mentions in offhand sentences in places that if you don’t happen to be looking at that exact page good luck finding it. this, too, felt like inadequate care and attention by el goog

I imagine if one is working with this every day you know the lay of the land and where to avoid stepping into holes, but wow was I surprised at how much it was possible to rapidly rakestep, given what the language pitches as