Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Flutter 3.47

flutter.dev

Post reply on HN
Print view View original

141–150 of 231 posts

Re: Flutter 3.47

#141

Post by pjmlp »

hypendev wrote: post #106
meerita wrote: post #81

I still prefer React Native with Expo over Flutter, mostly for practical reasons: * Language and hiring: TypeScript has a much larger developer pool. Dart is a solid language, but finding experienced Flutter engineers is harder. * Platform model: React Native maps much more naturally to native platform concepts. Flutter owns much more of the rendering stack, which is powerful, but also creates another abstraction lay…

As someone who used all these frameworks professionally for years, I highly agree. Although, I do not prefer Expo due to it's highly annoying build system and dependency hell, but React Native itself in that case. While I understand Google wants a horse in this race, Flutter doesn't feel like a horse to bet on. - Dart is a really _ugly_ language with lots of tiny annoyances. Its as if someone took worst parts of Java…

Google has two horses in this race, because Android team doesn't acknowledge Flutter and rather go with KMM and Compose, alongside JetBrains.

Re: Flutter 3.47

#142

Post by satvikpendem »

gman83 wrote: post #74
doodlesdev wrote: post #33

While I've used Flutter since Alpha, I've been away for a few years. A few things have shocked me in these release notes: how come Impeller still wasn't the default engine for all platforms? Also, why are they migrating to WASM if one of the core features of Dart is compiling to JavaScript? Finally, how come multi window support only get viable now, after four years having desktop support? Honestly, Flutter is an ext…

We've been hearing that Flutter is going to be killed any day now for almost a decade. And yet here we are, it's a stable platform that's quietly chugging along with massive 3rd party buy in. Honestly, Google could abandon it at this point and it would have enough momentum to keep going just fine. Where is Compose Multiplatform? Does anyone actually use that, is it even stable yet?

Some do use CMP but yes it's quite immature compared to Flutter and they'll spend a lot of time fixing the same bugs with rendering that Flutter fixed a while ago. We'll see how it goes though, if CMP becomes the blessed route for Android cross platform development it'll attract more people and attention.

Re: Flutter 3.47

#143

Post by pjmlp »

WA wrote: post #76
TheChaplain wrote: post #73

Are Flutter and React Native still viable choices today? I get the impression that more are going for native mobile, KMP or PWA.

Flutter: if you want a pixel perfect version of your app that looks similar on Android and iOS. Some quite popular apps use it and make a shit ton of money, for example Headspace. More here: https://flutterhunt.com/ React Native: totally viable, because core business logic is the same. If you want native UI elements and all the iOS Liquid Glass stuff, but don’t want to have to completely separate code based, React Na…

No one cares about PWAs, because mobile Web by itself is good enough without having to deal with PWAs boilerplate.

Re: Flutter 3.47

#144

Post by satvikpendem »

phist_mcgee wrote: post #122
wiradikusuma wrote: post #92

Earlier quoted context omitted.

You should try Dart/Flutter again, they've improved a lot. - Dart. It's richer than JS/TS with stronger type safety, and seems purpose-built for UI. Fewer Dart developers than JS, but I'd argue those JS developers cannot be immediately effective coding React Native (Expo) anyway. - Emulated components vs. real native components. For multi-platform apps, this is actually desirable. These kinds of apps have their own d…

They still haven't got native scrolling perfect for iOS. I used a big name app just today and I could instantly tell without looking it up that it was a flutter app, because the scrolling felt non-native.

This is fixed in the past few versions of Flutter, they likely haven't updated their SDK.

Re: Flutter 3.47

#145

Post by satvikpendem »

nmfisher wrote: post #139
hypendev wrote: post #106

Earlier quoted context omitted.

As someone who used all these frameworks professionally for years, I highly agree. Although, I do not prefer Expo due to it's highly annoying build system and dependency hell, but React Native itself in that case. While I understand Google wants a horse in this race, Flutter doesn't feel like a horse to bet on. - Dart is a really _ugly_ language with lots of tiny annoyances. Its as if someone took worst parts of Java…

> Dart is a really _ugly_ language with lots of tiny annoyances. Its as if someone took worst parts of Java and Javascript and turned them into a language. Terrible to write, terrible to read, terrible to use. While I’m a bit ambivalent towards Flutter, I totally disagree with you on Dart. To me it’s a better version of Java/Typescript with a very mature cross-platform and JIT/AOT compiler. Admittedly there are some…

They probably just haven't used the latest Dart versions which fixed a lot of the "ugliness" (which I'd call pragmatism but regardless) like primary constructors where a class can just be a single line now.

And I mean, their entire comment is a way to shill their app so I wouldn't take much stock in what they're saying.

Re: Flutter 3.47

#146

Post by kebsup »

If anyone is interested to see the WASM + canvas renderer performance compared to Android/iOS builds, I've build my app for the web.

The web app is here: https://app.vocabuo.com (completely free) And the links for Android/iOS builds are here: https://vocabuo.com (soft paywall)

To an untrained eye who does not care about dropping a few frames, the web version is almost indistinguishable from the "native" build. Especially if you add it to homescreen from safari to hide the navigation bar.

Re: Flutter 3.47

#147

Post by satvikpendem »

user43928 wrote: post #129
puelocesar wrote: post #111

Earlier quoted context omitted.

I was forced to migrate from pure native development to React Native and Redux is one of the stupidest things I ever witnessed. Or at least the way the previous devs setup that thing, because it’s so easy to make costly mistakes with it. I lost so many days of my life profiling and debugging to figure out why hundreds of components were re-rendering when a tiny thing changed somewhere completely unrelated

Redux is great and it solves exactly that problem. You create a selector. You use the selector in a React component. The component re-renders when the selector outputs a different value, with the usual reference equality caveat. Does it get any simpler than that? However, yes, I have seen most developers use Redux incompetently. They would use actions like "setOrder" instead of "itemAdded", defeating the purpose of a…

They might have been using Redux before it did a major API change in the form of slices.

Re: Flutter 3.47

#148

Post by satvikpendem »

palata wrote: post #87
meerita wrote: post #81

I still prefer React Native with Expo over Flutter, mostly for practical reasons: * Language and hiring: TypeScript has a much larger developer pool. Dart is a solid language, but finding experienced Flutter engineers is harder. * Platform model: React Native maps much more naturally to native platform concepts. Flutter owns much more of the rendering stack, which is powerful, but also creates another abstraction lay…

Out of curiosity, do you have any experience with Kotlin Multiplatform and Compose Multiplatform? I would like to know how that compares.

I have. It's still immature compared to Flutter and doesn't necessarily run native compiled code depending on platform, it can still be tied to the JVM. Not to mention how amazing pub is compared to Gradle.

Re: Flutter 3.47

#149

Post by brabel »

nmfisher wrote: post #139
hypendev wrote: post #106

Earlier quoted context omitted.

As someone who used all these frameworks professionally for years, I highly agree. Although, I do not prefer Expo due to it's highly annoying build system and dependency hell, but React Native itself in that case. While I understand Google wants a horse in this race, Flutter doesn't feel like a horse to bet on. - Dart is a really _ugly_ language with lots of tiny annoyances. Its as if someone took worst parts of Java…

> Dart is a really _ugly_ language with lots of tiny annoyances. Its as if someone took worst parts of Java and Javascript and turned them into a language. Terrible to write, terrible to read, terrible to use. While I’m a bit ambivalent towards Flutter, I totally disagree with you on Dart. To me it’s a better version of Java/Typescript with a very mature cross-platform and JIT/AOT compiler. Admittedly there are some…

Yeah I have no idea how someone who has used all these languages can come up with a conclusion like Dart is “uglier”. I really want to know what exactly they think is ugly about it!

Re: Flutter 3.47

#150

Post by phoghed »

oDot wrote: post #116

Does anyone know if the original promise of their simple layout model proved itself? IIRC, the Flutter team mentioned how using just width/height constraints is enough to represent all relevant layouts. This sounds very nice, being so much simpler than Flexbox and miles ahead of CSS Grid ergonomics. Did it live up to the promise or did they expand the model with Flex/Grid/etc?

The web almost got constraint based layout. Well maybe almost is too strong, but it was a candidate. CCSS.

We got tables and floats instead.

Post reply on HN