Live data from Hacker News

Google's cross-platform Flutter UI toolkit goes 1.0

techcrunch.com

221–230 of 343 posts

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#222
post #67

Writing plugins/bindings for native code in flutter doesn't look fun. Almost 100 lines of code to write binding for function that doesn't take any parameters and returns simple 'int' (int getBatteryLevel()). This just looks even worse than JNI to me. Don't want to even thing how long time it would take me to write bindings for function that do image processing. https://github.com/flutter/flutter/blob/master/examples/…

Some boilerplate to write a custom native plugin is better to me than the dependancy hell you get on ReactNative.

That being said - my personal usecase would like a direct C++ interop, and flutter is working on it. See https://github.com/flutter/flutter/issues/7053

Since flutter runs as native ARM they can directly call C++ instead of having an expensive JNI bridge on android. If you're wanting something fast with native processing - flutter will be the best option out there IMO if that issue is resolved.

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#223
Having using Flutter since the alpha releases, it's great to see how the framework has evolved to a production-ready release. Honestly, learning Dart isn't that difficult nor foreign if you're coming from a low-level language such as C#/C++/C or Java. Been enjoying using it since.

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#224

Earlier quoted context omitted.

Here's some of the explanation about why they chose Dart: > There’s a lot of nice properties of Dart, we talk some about this on our website at our frequently asked questions. One of the nice properties of Dart is that it has a really fast garbage collector, one of the choices that we made in Flutter was to have this reactive style system where it’s very common to allocate thousands of objects in a – if not, tens of…

No one uses Dart. No one is going to switch from React or Vue to Flutter when they can't bring over their TypeScript skills and tooling. It was a stupid, arrogant decision on Google's par, end of story.

As someone who use Java a lot and don't favor Javascript I'm grateful there is Dart.

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#225
post #144
post #74

Earlier quoted context omitted.

> We are on the verge of VR and AR and I don't see how flutter can help e.g. processing >100fps Video Feed using OpenCV library. The demo they presented on stage with ML and smile detection had quite big latency. I wouldn't call it real time. I can't find any claim from Flutter team that 100fps video processing is even their goal. So that's a strange metric to measure it by - especially since it's competing against J…

I have recently gave a look at Qt after 5 years and it seems lots of things have changed for the better. You get the same hot reload like flutter when modifying GUI using QML (with V-Play you can even hot reload not just on simulator/emulator but on real device). Qt material theme has good look and feel. Sadly iOS theme is a little bit lacking. C++ is probably not the most productive language to write business logic…

You can also use .NET Core (instead of python) with QML/Qt.

https://github.com/qmlnet/qmlnet

note: I'm the author.

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#226
post #94
post #74

Earlier quoted context omitted.

> We are on the verge of VR and AR and I don't see how flutter can help e.g. processing >100fps Video Feed using OpenCV library. The demo they presented on stage with ML and smile detection had quite big latency. I wouldn't call it real time. I can't find any claim from Flutter team that 100fps video processing is even their goal. So that's a strange metric to measure it by - especially since it's competing against J…

> On mobile? Qt really isn't pleasant or usable on mobile. What's wrong with it?

QtWidgets aren't really geared for mobile. QML however is fine

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#227

One of the main issue with Flutter is that you can't embed a native view inside a flutter widget tree. This makes it limited as we can't have inline maps or custom video views. There are people working on it. The progrss has been slow. I checked a couple of weeks ago and the issue was still open. But as far as I know you can have a native view in its own activity. Though not a blocker for simple apps which previously…

I think this is one of the things they announced today, search for "Platform Views": https://developers.googleblog.com/2018/12/flutter-10-googles...

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#228

The widget layer of flutter is Skia which is written in C++ and Flutter apps compile to ARM binary (native) code. Someone else asked about whether a Flutter app can be ported to Linux; why not compile both the logic and the UI directly to WebAssembly?

WebAssembly compilation is a little orthogonal to getting the framework and rendering system up and running. We do not have to wait for WebAssembly to make progress on the UI side of things. Having said that, when WebAssembly is available for us to try, we certainly will.

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#229
post #67

Writing plugins/bindings for native code in flutter doesn't look fun. Almost 100 lines of code to write binding for function that doesn't take any parameters and returns simple 'int' (int getBatteryLevel()). This just looks even worse than JNI to me. Don't want to even thing how long time it would take me to write bindings for function that do image processing. https://github.com/flutter/flutter/blob/master/examples/…

How is the UI/UX differences between android/iOS apps handled with flutter?

e.g. iOS HID requires navigation buttons for obvious reasons & not so for android.

Re: Google's cross-platform Flutter UI toolkit goes 1.0

#230
post #151
post #134

Earlier quoted context omitted.

Same in the desktop world - Qt emulates the widgets, but can theme them, then QML is another story. Also WPF (from what I've heard) uses (skia?) to paint own widgets. IMGUI is another example. Then using the native wrappers, like wxWidgets is often cumbersome to create customized control, and if you do you end up with some platform specific version (not end of the world, but pretty much why not use the OS toolkit dir…

WPF uses DirectX.

Thanks! Makes sense if it uses DirectX, not sure why I got skia into this :)
Post reply on HN