Ready for Production Apps: Flutter Beta 3 • Hacker News Board

Re: Ready for Production Apps: Flutter Beta 3

#11

Post by quangio » Sun, Jun 03, 2018, 5:45 AM UTC

grigy wrote: post #10

hliyan wrote: post #8

Earlier quoted context omitted.

I've been a React fanatic for several years, so my opinion is colored by that: 1. Great DX (developer experience) - a single language (Dart); no need for JSX, JavaScript, JSON, Flux/Redux and various other libraries. You can focus on the business logic rather than battling the ecosystem. 2. A single set of components (no iOS or Android specific navigator components etc.) 3. No longer need a JS engine to run - truly n…

Being agree with all 4 points I see two drawbacks: 1. Not using OEM widgets. Even the rendered widgets may look good, they can't beat the native widgets optimized for the particular platform. 2. The choice of Dart as the main language. I can understand both points though

I don't think using non-OEM widgets is a bad thing because it's not like Electron; Flutter uses Skia to render widgets, and it's fast. There is an article https://medium.com/flutter-io/why-flutter-doesnt-use-oem-wid...

Re: Ready for Production Apps: Flutter Beta 3

#12

Post by threeseed » Sun, Jun 03, 2018, 5:45 AM UTC

ma2rten wrote: post #6

saagarjha wrote: post #3

> Alibaba praises Flutter for its consistency across platforms As a user, I don't. Sure, on Android Flutter looks OK, but on iOS it looks out-of-place.

There is an iOS theme (Cupertino), but I am not sure how complete it is.

The available widgets are shown here:

https://flutter.io/widgets/cupertino/

Re: Ready for Production Apps: Flutter Beta 3

#13

Post by brunoluiz » Sun, Jun 03, 2018, 5:46 AM UTC

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.

Re: Ready for Production Apps: Flutter Beta 3

#14

Post by falcon620 » Sun, Jun 03, 2018, 5:52 AM UTC

I keep checking up on issue 730 once in a while:

https://github.com/flutter/flutter/issues/730

Nope. Still no inline webview component.

Re: Ready for Production Apps: Flutter Beta 3

#15

Post by hazz99 » Sun, Jun 03, 2018, 5:53 AM UTC

A few months ago, I began using Flutter for a sideproject (That I wanted to release).

Although the developer experience is absolute fantastic (And definitely the future), the plugin ecosystem is extremely lacking. I wanted to use AWS, and there was 0 backing for it. Since I didn't want to interact with raw AWS APIs, I moved to React Native.

Re: Ready for Production Apps: Flutter Beta 3

#16

Post by skolemtotem » Sun, Jun 03, 2018, 6:02 AM UTC

hliyan wrote: post #8

everdev wrote: post #4

Earlier quoted context omitted.

I'm evaluating it. Why do you think it's the future? What's the feature you value most?

I've been a React fanatic for several years, so my opinion is colored by that: 1. Great DX (developer experience) - a single language (Dart); no need for JSX, JavaScript, JSON, Flux/Redux and various other libraries. You can focus on the business logic rather than battling the ecosystem. 2. A single set of components (no iOS or Android specific navigator components etc.) 3. No longer need a JS engine to run - truly n…

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?

Re: Ready for Production Apps: Flutter Beta 3

#17

Post by myguysi » Sun, Jun 03, 2018, 6:11 AM UTC

skolemtotem wrote: post #16

hliyan wrote: post #8

Earlier quoted context omitted.

I've been a React fanatic for several years, so my opinion is colored by that: 1. Great DX (developer experience) - a single language (Dart); no need for JSX, JavaScript, JSON, Flux/Redux and various other libraries. You can focus on the business logic rather than battling the ecosystem. 2. A single set of components (no iOS or Android specific navigator components etc.) 3. No longer need a JS engine to run - truly n…

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?

You’re right, it gets compile to native code

Re: Ready for Production Apps: Flutter Beta 3

#18

Post by myguysi » Sun, Jun 03, 2018, 6:14 AM UTC

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.

Probably marketing, that’s the one thing that bugs me about Flutter and React Native. They’re not as big as the hype would have you believe

Re: Ready for Production Apps: Flutter Beta 3

#19

Post by martalist » Sun, Jun 03, 2018, 6:36 AM UTC

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.

and/or less Angular 2 adoption.

Re: Ready for Production Apps: Flutter Beta 3

#20

Post by alfonsodev » Sun, Jun 03, 2018, 6:57 AM UTC

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 native development yet, make two "boring" applications in kotlin and Swift and learn the native platforms. Long term you'll be a better more complete app developer. Later if you want to try flutter or react-native you won't be locked by what plugins can do.