In two companies we already gave up on Dart and Flutter because of how it's backwards incompatible is. The language and frameworks moves very fast, it develops new tools and classes before the old ones become mature enough and adopted by the industry. Then suddenly, Flutter 27 lands, requires Dart 45, which requires intl 81.2.5. and now you can't compile anything anymore. Whole upgrade process, tools, compiles and libraries are broken for months before Google and OSS catches up. Once ecosystem is on Flutter 27 your upgrade path takes weeks, because a core method was renamed or compiler flag removed and CI/CD is failing. So you just move back to Java and Kotlin, where code from 2012 still compiles and works just fine.
I released two apps built in dart on flutter. I loved it at the time, but I ran into this issue headlong with both of them. Release v1.0, move on to other things, come back in a year with a new computer to fix a minor bug and I can’t even compile the original release anymore, and had to spend forever rejiggering everything to get it back to the state it was when I left it. I really loved dart, and even flutter, building in it was a breeze. But the churn made the js ecosystem look slow.
You don't get to very rudely accuse someone of giving "fake examples" (why?) and then, later, use weasel words like "in my experience." Perhaps your experience isn't representative of everyone else's.
None of those versions exist, so the example is obviously made up.
Now, it could still be rooted in reality rather than being a complete fabrication. But when all the provided details were made up, it's basically impossible for anyone to check.
