I remember Swing, Flash, Web Forms and Java Applets and I have never worked with any of them. The likelihood that we are still writing Android applications 10 years from now is low. Going beyond the simple arguments, the viability of Flutter is in the fact that it allows you to basically build whatever you want, wherever you want, without seriously sacrificing performance. One can make a serious argument about app size but that's about it. If the real-world performance of a Flutter application is close to native, then there's not a strong argument. It's important to always consider real-world metrics when discussing performance. If that were the case, why would Kotlin exist and have flourished as much as it has in such a short time? Dart was directly inspired by Java & C# as well, so bashing it coming from either seems silly.įlutter has already proven in some cases to outperform and keep up with native. Saying that Java is better than anything after 2010 is subjective. To discredit this approach is to discredit every game built on Unreal or Unity and every application built on RN, PhoneGap, Xamarin, etc. Last year I attended an Android conference where developers wouldn't even attend flutter talks because of fear of alienation from their peers.įlutter's approach of rebuilding native widgets and shipping apps with the framework is not new. ![]() This also represents the mob mentality that developers tend to have, unfortunately. ![]() It normally means that they've never seriously examined whatever they are criticizing. When developers approach technology with such vitriol and no hard evidence, I question their viability.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |