FFS this right here should be a core guiding principle for everyone. Not enough people align this way.
Yes but looking on the most of the people they may have problems developing in different languages. For me it makes no big differences developing in Swift, Java, Kotlin so I can develop for all platforms with good and fast results. But many people are not able to do that for example while they donāt want to spend that amount of time. Thatās why so many people like platforms like Xojo. One language for all. But a dump ecosystem and many, many Bugs and missed features. And for this people there should be also a solution outside of the Xojo world.
One of the problems is for sure that they may have not for all platforms a visual designer. For mobile and web it makes not so much sense to habe one. In my eyes that is one of the borders people are considering not to use other tools.
For me it is no problem to develop UI without a visual designer. But many people told me that even the missed UI Designer is a problem. Even if we speak about declarative UI. That makes the world much smaller for the Developers.
So people decide not while it is technically for them a good solution. They decide while it is more simple to develop with a platform.
The context I was intending but left out: the other end is sometimes an interviewer gets pissy about which languages were used for past projects. Sometimes even unrelated to the position: its just their pet language. ie: C# position asking about tailwind. 
And I say the similar to āthere is no best way but the needed way for the project.ā
Returning to the topic of Flutterā¦ We're forking Flutter. This is why.
I doubt they will stay for long time. Flutter is a real big project and a real high amount of development costs. Changes in IOS and Android are not rare at all and the platform has to be changed every now and then. It could be a nice project. Letās see what happens after three years. The point is always the need of being actual with the OSses
1 Like
the fork is really interesting, for the sorts of conversations they want to start.
matthew had a conversation with viktor, from serverpod, this afternoon, discussing it.
serverpod is a docker framework for writting backends in dart. it has an orm, rpc-interface, postgre connector, etc.
Iāve got tired of pushing the guys to āfixā their eternal desktop alpha support doubled as release, and then batches of layoffs on several teams only made my belief that Flutter was going downhill grow. I simply abandoned my investment of study and efforts on that platform the day I saw them resetting crucial tasks to very low priorities. Something like Flock needed to happenā¦ now weāll see if it boosts or kills Flutter for good.
Even Google is decrying its own investment to favor another solution:
get on mattās (@superdeclarative) thread on x and mention desktop. imho itās the most obvious thing for them to hit
He knows, thatās one of the main reasons he decided to fork:
āGoogleās corporate re-focus on AI caused the Flutter team to de-prioritize all desktop platforms. As we speak, the Flutter team is in maintenance mode for 3 of its 6 supported platforms. Desktop is quite possibly the greatest untapped value for Flutter, but itās now mostly stagnant.ā
His words.