One thing that LLM-based development brought that I didn't predict but makes perfect sense:

There's hardly any "ecosystem envy" anymore.

If there's a great library in {Python, TypeScript, C#, Java}, with unit tests, and you want it in Dart — just ask an AI to port it for you.

#dartlang #flutter

If the library being ported is solid, then the result will probably be better than many of the human-made ports you can find on pub.dev (including the ones I made myself). With TDD and well-scoped libraries, porting is well within the capabilities of the average models out there. LLMs are fantastic at translating from one language to another.

@filiph There are plenty of slop translations on pub.dev too, though. These are all literal translations of the source library and miss what makes Dart so nice (like composing with streams, sinks and converters, or using the type system effectively).

But to be fair we've had a good share of those well before LLMs. So as usual it's gotten easier, but knowing what you're doing is still key.

@simonbinder

> These are all literal translations of the source library and miss what makes Dart so nice

I would also much rather have libraries that are made from the ground up by Dart programmers in proper Dart style. But, FWIW, if I can't have that but there's a well-tested non-dartisan library, I'll take that.