![]() ![]() There is rarely any iOS app that use native widgets without completely changing branding and styling.ģ) Comparing to SwiftUI, new Material 3.0 feels more complete - there is more widgets and navigation choices. On the other hand SwiftUI and Material 3.0 looks more modern. Few observations:ġ) Difference between new latest Material You (aka material 3.0) and SwiftUI is smaller than Material 2.0 and UIKit - at least regarding look & feel.Ģ) I find old UIKit style quite boring same with older material 2.0. I'm iOS dev but right now learning flutter. "Only a fool would use the best tool for the job", is the implication of those who disparage Dart. The argument seems to be that at least if you're using the same crappy tool for everything then you can claim the efficiency of never having to change your tool. Those who would give that answer consider Javascript, on the other hand, an (inferior) tool not only for this problem, but also for other problems, so it is the more generalizable tool and therefore it makes more sense to use Javascript. To which the answer I keep hearing is "it is only superior for doing the thing it is built for - it isn't superior for other things." If there is one repeated comment I hear about Flutter it is "wow, it seems like such superior technology, I wonder why it isn't more widely used". Sure, you could just assemble a big pile of rubble and scramble up it to get on the roof, and it is true that you might be able to later use the rubble for other purposes (whereas a ladder is built for a specific purpose) - but that does not make the ladder the more limiting tool. An entire team at Google literally created a language to make it easier for you as a developer to express yourself in this domain, and you think that's a drawback? That's like thinking being given a ladder is a drawback when you want to get up on the roof. ![]() You're not supposed to use Dart for any purpose other than Flutter - that's not a drawback to learning Dart - that's the whole point. ![]() They decided to make the design of Flutter as a framework so clean and pure that they would have to work backwards to figure out what language it would need to be written in and then they created Dart. You seem to think that the framework designers at Google just decided to pick a niche language called "Dart" to write Flutter in when they could have picked Javascript to write Flutter in. Think of it the other way around: Dart was created for the sake of Flutter. I’ve seen some profound growth in the area over the last two years. The one real complaint I can agree with is that the ecosystem kind of sucks, but it’s growing and getting better. ![]() But I’ve long since crossed the threshold in my mind, and now I can strongly say I don’t want to program UIs in anything else again. (But in case he’s listening, please add Rusts discriminated enums, it really hurts to move from a language with them to a language without them.)Īs for Flutter, as a WinForms and UWP developer, coming to terms with its Dart-declared UIs was tricky, especially when coupled with the constraints based layout system. I also know here is a principal developer of the language, and he’s done a good job. Clean, fast enough, and to my experience so far, footgun free. I really think Dart is one of my favorite languages, it’s just a joy to work in. For reference, my background is in OOP/JavaScript land, with patches of Scheme, Rust, and way more Go than I ever wanted. I think of Dart as being C#-lite, although the latest changes with class modifiers have somewhat complicated the sentiment. I have little to add to the article in question, but I’d like to say that I’ve fallen quite in love with Flutter and Dart. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |