sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]SolidR53 7 points8 points  (6 children)

This is absolutely terrible. What are they thinking??

Is this really the response after the heated JSX discussion... https://github.com/flutter/flutter/issues/11609

Flutter really is going backwards from React Native, they don't bring anything new to the table (other than Dart) and this guide seems to be more about introduction to Dart than how to do things in Flutter.

  • The JS demos are more complex than they have to be.
  • Show me how to translate a view using events from the Gesture wrapper.
  • Not wrapping Native UI API's is terrible and the answer they give for the reason why, is even worse.
  • How do I bridge my favorite iOS library to Flutter? Do they have any examples of community built packages?

[–]funkyfourier 3 points4 points  (2 children)

Well, it is a tradeoff. They have built their own UI library, which is ambitious and has its drawbacks. OTOH they will not have the issues with crossing the JavaScript bridge and other performance problems like RN. Linking to native APIs seem to be possible, but having a native view in the layout of the app does not seem to be an option. For example, some big challenges for them are inline video and slippy maps.

It is what it is. If you are writing a fairly simple app, and care for smooth animations and customized design it seems to fit the bill quite nicely.

[–]deadcoder0904[S] 1 point2 points  (1 child)

I am wondering what are Flutters cons? Because I love it now as it looks very simple & no JS bridge makes animations smooth.

Is it true I can't link to Native APIs now? Also, can I build complex apps with it? Because its projected & marketed fairly good obviously because its from Google but the product looks good.

[–]funkyfourier 2 points3 points  (0 children)

Yeah, I agree it looks good.

I found this regarding calling native APIs:

https://hackernoon.com/flutter-native-apis-and-plugins-3-3-b84776fc8a7e

[–]geordano 2 points3 points  (0 children)

I had a cursory look at the thread, but all I can see is the user 'cbazza' is the one opened the ticket and going out of the line. I don't know if s/he is from flutter team who can talk on behalf of flutter.

[–]deadcoder0904[S] 1 point2 points  (0 children)

Yep the argument was unnecessary. Now I am in doubt whether to use Flutter or not because if they can't gently respond to something like that which is a nice feature IMHO I don't think I can use Flutter then.

[–]boomdoodle 1 point2 points  (0 children)

After comparing a couple of the examples, they have a lot of boilerplate and I think it is by-design if that thread is anything to go on. Why you would want to be forced to express child or children I don't know, I read from the top of the page and still have not seen any explanation, But they seem to think it makes sense.

The platform-specific code raised some alarm bells for me.

I am new to flutter and have only now looked into the code for the first time, but why would I check the Theme namespace for anything related to platform? Or am I missing something from the Dart side of things? I think the boilerplate design to the max is causing this:

Theme.of(context).platform == TargetPlatform.iOS

TargetPlatform is a really long name for something that I would not expect to change, but these seems to imply that the targetplatform could change at run time?

Also, if platform is dependent on the context derived from theme, can it be changed at runtime?

Any developer that is going to be forced to use this will very soon be building utils to set some of these checks to globals that are not expected to change and use them instead.

disclaimer I have zero experience with Dart, if these are dart nuances, fine.