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

Ready for Production Apps: Flutter Beta 3

developers.googleblog.com

Post reply on HN
Print view View original

41–50 of 107 posts

Re: Ready for Production Apps: Flutter Beta 3

#41

Post by kmonsen »

vertex-four wrote: post #40
RyanZAG wrote: post #37

Earlier quoted context omitted.

Chicken and egg, right? If Google declares it not ready for production, then nobody uses it for production apps, so it never gets the kind of testing it needs to really be production ready. If Google declares it out of beta, then people assume nothing will change, and if things do change they complain. So the current wisdom is to have a 'production ready beta' which indicates an in-between period where things can cha…

Wouldn’t that traditionally be a Release Candidate? Something you think is good to go, but needs wider testing before you can say that for sure?

I think with release candidate there is only bugfixes later, but with the beta the door is left open for API changes etc.

Re: Ready for Production Apps: Flutter Beta 3

#43

Post by conradfr »

wokwokwok wrote: post #5

This has been posted 4 times before with zero interest in it when it was announced a month ago. Did something change? Did someone just want an excuse to talk about flutter for a bit? I'm quite opposed to this 'post random link on topic X because I want to talk about X' thing. If you want to talk about flutter at least bother to find something which is technically interesting to read. This is just marketing talk.

Maybe because of this tweet https://twitter.com/sandofsky/status/1002637340291018754

https://news.ycombinator.com/item?id=17216628

Re: Ready for Production Apps: Flutter Beta 3

#44

Post by sebe »

foepys wrote: post #34
egeozcan wrote: post #29

Earlier quoted context omitted.

The problem is that the accessibility work already needs to be done on every platform (for now we have two really popular ones but nobody can be sure what the future brings). Also, if you could just recompile your app for a new platform and release (more or less), it would remove the biggest barrier to entry for possible new platforms: Adoption.

That's not what I meant. Android and iOS already have their own widgets with accessibility features in place. iOS even better than Android. It took years for them to develop to where they are now. Now Flutter is making its own widgets that look and handle like the corresponding native widgets. So they need to implement accessibility all over again in the same way that is already present on the platforms. Google is th…

I think accessibility was a requirement for an internal google flutter app, have you had a chance to look at https://flutter.io/accessibility/

Re: Ready for Production Apps: Flutter Beta 3

#45

Post by bsaul »

Apple really need to react if they want swift to get any traction. IOS hasn’t had any major UI update since iOS7 , and android is a mess anyway, so using a cross platform now makes more sense than ever. The icing on the cake would be to have a path for reusing dart business layer between flutter and angular.

That’s a really promising stack.

Re: Ready for Production Apps: Flutter Beta 3

#46

Post by hknd »

brunoluiz wrote: post #13

Fun fact: on pre-release Angular 2 versions, Dart was it's main language. My hypothesis is that, if they decided to continue using Dart, probably we would have more Dart developers and this could have lead to a faster Flutter adoption.

angulardart (1) is still available, but probably not used by any serious project. Still have mixed feelings about dart - apparently some of the biggest frontends at Google (advertising) use this, so it must do something really good.

1: https://webdev.dartlang.org/angular

Re: Ready for Production Apps: Flutter Beta 3

#47

Post by cutler »

alfonsodev wrote: post #20

This all sounds very cool until you need something in your app that is not provided as third party module yet, or numerous third party plugins that you are using start being unmaintained or buggy or they don't support your use case. Then you'll need to write your own plugin in native language, but you have been writing in Flutter and you don't know enough about the native platform. My opinion, if you don't know nativ…

Learn Swift+iOS & Kotlin/Java+Android then Dart/Flutter. How many lifetimes is that to become deeply proficient?

Re: Ready for Production Apps: Flutter Beta 3

#48

Post by pritambaral »

tybit wrote: post #35
skolemtotem wrote: post #16

Earlier quoted context omitted.

How is it native if you're just replacing a JavaScript VM with a Dart VM? Or is the Dart somehow compiled to native code?

Dart has a VM (with hot reloading) for dev time and an AOT compiler for release builds. I’d say that’s one of the most attractive things about Dart to compensate for yet another language.

How large and invasive is the Dart runtime though? Running in a VM and running with a runtime are only so far apart. And I'm interested in distribution package sizes too.

Re: Ready for Production Apps: Flutter Beta 3

#50

Post by hawski »

How good is FFI in Dart? I mean how fast and easy is it? I see that it can call C and C++ libraries, but that's nowadays a basic requirement for any FFI. I'm looking maybe for an opinion and maybe some kind of numbers to back up it's performance.

As far as I understand it on Android it's compiled to a CPU native binary and has to use NDK and JNI to do anything. If that's a fact it's funny that on Google's own platform it has to go through two FFIs - Dart to C to Java. While on iOS just one - Dart to C, because what's there not to it for Obj-C?

I'm dreaming for a truly native everywhere platform. Something that would compile to DEX or JVM byte code for Android, CLR on Windows and a binary everywhere else. While using native widget toolkit for each platform - practically without any FFI. Also respecting HIG of each platform. Yeah, I'm a dreamer.

I heard about https://www.elementscompiler.com/ , but I would also like for it to be open source. :P

Post reply on HN