IMHO, some people just really want Dart and Flutter to fail, so they post the same tired doom prophecy in hope it will become self-fulfilling.

What is also annoying is that they come to normal Dart/Flutter related threads just to spoil them.

Meanwhile, the ecosystem grows, more and more people and companies choose Dart and Flutter and have fun creating software with this excellent toolchain.

The dogs bark, but the caravan goes on, as they say.

[flagged]

I think I had it confused with dart:html, which looks almost the same. I don't see a big difference in the example code.

Sure, whatever.

The one major company backing a project lays off a number of the team working on the project.

That is not exactly the signal of a bright future.

That's exactly the post that confirms the layoffs and that Google moved some clueless extras to fill the gap. Which means the core maintainers were laid off. If one think that removing the main team of a project won't affect its speed and quality, one is absolutely delusional.

exactly. Borland era OOP gui code was amazingly well thought out. The flaws in the flutter framework are soooo many, a lot of half baked things are made standard. Try to get 2-way scrollbars working decently (try to nest them, or go watch the video tutorials that supposedly explain how to do this - it was an absolute horror show). There are so many hassle factor things that one googles or searches the github for, find tons of other smart people beg for it with examples and use cases and just watch the team say they won't implement for some or other reason. But even the simplest thing, that when you create a component (say with mutable state) - you don't create one class to get one widget defined, noooo you have to create two, one stateful and one stateless. All of these little weird decisions that were made for bs reasons eventually add up to a ton of incidental complexity. Oh we made part immutable for "performance" reason, but the real reason is that people don't understand when to avoid functional style programming idioms. All the weird ways the layout system can bite you, the way they designed constraints being passed down and sizes passed back up - boy are they forcing you to do a lot of thinking about incidental complexity, and the different containers and how thy interact in ways you would not expect by default. The fact that you cannot on a per container basis disable overflow displays in dev (many people have asked for this). That silly debug ribbon your app gets until you disable it LOL who thought that was a good default. In the end though one can make it do a lot, and it is reasonably performant. But the pitfalls are many, and basic stuff that it doesn't solve well for you.

I just can not for the life of me understand the mentality of someone who themselves knows full well this isn’t a topic they are an expert in will jump into the middle of a conversation about it, spout nonsense and when they are corrected that what they are saying isn’t actually true chooses to double down on it rather than just accepting they had some bad information.

It’s just incredibly weird behaviour and yet, almost every time I’ve seen a conversation about Dart or Flutter on here for the past year or two I keep running into the EXACT SAME situation and made up stories like what you did today.

I can't find Dart or Flutter on that site.

Even if I could they tend to exaggerate to make the list more impressive. E.g. they include stuff that has just been rebranded or changed form a little (Chromecast) or even things that were obviously one-offs (Google Cardboard??).

You're just spewing misinformation at this point, GP just debunked everything you said by a comment from the flutter team. What's your goal here ?