Live data from Hacker News

Flutter 2

developers.googleblog.com

251–260 of 780 posts

Re: Flutter 2

#251

Flutter is winning the race in cross platform development. I have been using Flutter for past few days, and I really like the package on whole, tools and community. Having used Xamarin and Qt in the past, Flutter is a lot easier to learn.

I'm curious, when you refer to Qt, do you mean the QWidget application approach or QML? QML is much more like Flutter (but is indeed somewhat arcane to learn how to work with).

Re: Flutter 2

#252
OT but I recently did some research on cross platform desktop application development for MacOS and Windows.

Here's the options I found.

- (language: Pascal) Delphi applications can now run on both Windows and MacOS.

- (language: Python or C++ and QML) Qt applications work on MacOS, Windows and Linux..

- (language: JavaScript) React native is being ported by Microsoft to both Windows and OSX.

- (language: Kotlin) Kotlin now has "Jetpack Compose" for desktop targeting Windows, MacOS and other platforms. It's like "React for Kotlin".

- (language: C#) Microsoft Xamarin applications can target both Windows and MacOS.

- (language: JavaScript) Electron lets you run your web applications as desktop applications on Windows and MacOS.

- (language: Dart) And now Flutter can be added to the list of ways to build cross platform desktop applications.

- (language: Java) presumably this is Java's forte but I did not look into it.

- (language: Kotlin) TornadoFX - JavaFX framework for Kotlin https://tornadofx.io/

Re: Flutter 2

#253

Earlier quoted context omitted.

[Flutter Eng. Dir. here] Still relatively early days for Flutter Web, so I would not be shocked if it's not buttery everywhere. However, we would certainly love to learn more. fluter.dev/support has links as to how to file an issue if you're interested. https://flutterplasma.dev/ is one demo to try. We expect to be updating flutter.dev/web and flutter.dev/showcase to update more over time.

Have you ever tried one of your demos in Firefox on Mobile and Desktop? They're completely unusable in Firefox. For example, it only scrolls 3 pixels per rotation of the scroll wheel on Windows 10

Firefox is on the Google chopping block. They won't admit it but they're killing it by a thousand CSS cuts.

Re: Flutter 2

#254

We're all complaining about how js is a bad language, tooling is a mess, and how the web is fundamentally built for documents and makes it hard to create app-like experiences. Now, Google comes and creates a whole new UI toolkit from scratch, couples it with a very beautiful SDK and component framework and offers a far better programming language than js could ever be but we're still nagging. I was also pretty disapp…

> Now, Google comes and creates a whole new UI toolkit from scratch

Worth remembering that this is not the first or even second attempt at this from Google. So I think people are fair when they are not just jumping along all happily as people have been burned before.

Re: Flutter 2

#255

I want to love Flutter. But once looking at it, it's a no go. It's the new flash. Really, you cannot copy the text anymore. React native is my goto solution now.

Flutter team member here. In Flutter, the developer consciously decides which text should be selectable (and thus copy/paste'able), so while it's true that text is not inherently selectable in a Flutter app, text that the app developer decided to make selectable will be.

I get that user-select was already a thing in CSS, but why is so much of the text in the demos at https://gallery.flutter.dev/ not-selectable? It's a real bad look.

Re: Flutter 2

#256

The idea sounds very appealing, especially to an indie developer: being able to ship your app on multiple platforms from a single codebase is kind of the holy grail. Unfortunately, the result is.... I tested this Flutter example[1], on a 16" MBP with and i7, and it is janky as it can get, it feels like I'm using a 15 year old computer. From the code it looks like the whole thing is... rendered on canvas? I'll pass. […

works fine on Ubuntu 20.04 / linux (4year old i5)

Re: Flutter 2

#257
post #41

> Google Pay switched to Flutter a few months ago for their flagship mobile app, and they already achieved major gains in productivity and quality. By unifying the codebase, the team removed feature disparity between platforms and eliminated over half a million lines of code. from pay.google.com > Starting April 5, you won't be able to use pay.google.com to send and receive money from other people. To send and receiv…

It's not clear what you're arguing for or against. Google Pay is a product with multiple features and one of them is being phased out. What's that to do with the benefits they're claiming from the rewrite of the mobile app?

"I have a website and a mobile app. I unified my codebase with Tool X and saved a million lines of code!"

"Didn't you simply delete the website?"

"Yeah, what of it?"

Re: Flutter 2

#258
All the highly optimistic claims from the blog post and HN comments would be a bit believable if someone could just show us a web demo that doesn't suck hard. Or show us something accessible at the very least.

Re: Flutter 2

#259
post #137

Earlier quoted context omitted.

This sounds awful. Like some sort of bullshit DRM in a way. Now I'm thinking of all the ways I could get screwed here. * Not being able to copy transactions from my bank account * Not being able to easily send text to a read-later service (not sure if this necessarily depends on selectable text, but who knows, maybe selectable means the text isn't visible to these services now) * Not being able to easily copy somethi…

You know devs can already make text not selectable on the web, right?

Flutter should pick sensible defaults, in this case most agree that text should be selectable

Re: Flutter 2

#260

I want to love Flutter. But once looking at it, it's a no go. It's the new flash. Really, you cannot copy the text anymore. React native is my goto solution now.

Flutter team member here. In Flutter, the developer consciously decides which text should be selectable (and thus copy/paste'able), so while it's true that text is not inherently selectable in a Flutter app, text that the app developer decided to make selectable will be.

Oh boy, that is a spectacularly bad idea.

Not only is this making it easy for app developers to do the wrong thing ("I will just put some text here and make it unselectable, that is going to be great UX") but even worse, it is the default?

There are going to be some unintended consequences here, I suspect.

This reminds me of those websites that use javascript to preventing pasting into password fields "because security", thus breaking everyone's password managers, and making everyone less secure in the process ("if I have to type in that password every time, I'd better choose something simple I can remember...").

So, what about accessibility? If the text is not accessible, how are screen readers going to work?Vision impaired people are just going to have to ... do what, exactly? Will they have to apply OCR to access the content of a Flutter app?

This really reminds me of what was so sucky about Flash. I guess we'll get lots of little walled gardens that make basic interaction via text deliberately difficult. This feels like the opposite of the open web.

Post reply on HN