Live data from Hacker News

Flutter 3

docs.flutter.dev

301–310 of 453 posts

Re: Flutter 3

#301

Despite many maturity issues in practice Flutter is the only realistic option for true cross platform UIs that run everywhere. Apart from Qt , but the licensing issue is a hindrance. And yes, the web backend isn't ideal, but it will improve over time. I just wish Google had built Flutter on a low level core that isn't tied to Dart, so it would be usable from other languages. Dart isn't horrible and is getting better,…

"I just wish Google had built Flutter on a low level core that isn't tied to Dart, so it would be usable from other languages." Exactly. Dart is a deal-breaker. I was tasked with choosing a cross-platform development solution, and rejected Flutter because nobody at my company (including me) knows Dart or has time to learn it. Nor would any contractors we were likely to find know it. After quite a bit of research on o…

Flutter and Dart seemed to have been internal tools built by engineers looking for an interesting project to spend their time on while at Google.

Kotlin swelled up around the limitations of Java 8 in outside organizations and took over the ecosystem so Android devs could be productive while Google was fighting with Oracle

Re: Flutter 3

#302
post #90

Earlier quoted context omitted.

I’m confused, do you not use desktop apps?

How many new desktop apps do you use (first released in the past ~5 years or so), and how many of them aren't Electron? Desktop GUI software is a pretty small niche. The web has eaten nearly everything, and games don't use native UI stuff.

The post I replied to implied that the rate of production of them is decreasing, and you are claiming this too. I’m not convinced about that.

Re: Flutter 3

#303
Flutter is great for cross-platform UIs.

I found it a bit difficult to work with, and I also wanted to code my UIs from the back-end. So I wrote DocUI which will be released in the next month or two. https://nexusdev.tools

Re: Flutter 3

#304
post #151

Earlier quoted context omitted.

I think the decision of which cross platform technology to use mostly depends on a team's preferred tech stack. C++ -> QT C#/.NET -> MAUI/Blazor JS/Web -> React.Native/Electron Dart -> Flutter This is what I think is holding back Flutter -- that it wasn't built on an incumbent technology. Because Dart doesn't have quite the following, it has to evangelize itself a bit more than the other options.

Kotlin -> Jetpack Compose > Native Android, Native iOS (KMM) and soon Desktop+Web (Compose Multiplatform)

[deleted]

Re: Flutter 3

#305

Despite many maturity issues in practice Flutter is the only realistic option for true cross platform UIs that run everywhere. Apart from Qt , but the licensing issue is a hindrance. And yes, the web backend isn't ideal, but it will improve over time. I just wish Google had built Flutter on a low level core that isn't tied to Dart, so it would be usable from other languages. Dart isn't horrible and is getting better,…

It's not remotely a realistic option. CJK is all second class citizen. I just tried their latest demos. Tried to enter 日本. It utterly failed. First it's still trying to draw on it's own so you get to see some placeholder □ while typing. Then, it effup and typing n-i-h-o-n kept producing Nいほん on this example

https://gallery.flutter.dev/#/demo/cupertino-text-field

As long as they keep insisting on rendering everything themselves instead of relying on the OS/DOM Flutter will always be a poor choice for UI

Re: Flutter 3

#306
post #56
post #27

Flutter 3 comes with an upgrade to Dart 2.17 [1], which has quite a few improvements as well... including state on enums. While that's great, I was hoping it would be like in Rust, where each enum variant can declare its own state components, but unfortunately it seems to be more like Java: same state for all variants. Well, at least there's quite a few other small but useful improvements... and they showed how they…

> While that's great, I was hoping it would be like in Rust, where each enum variant can declare its own state components, but unfortunately it seems to be more like Java: same state for all variants. As much as I like Rust’s enums, I think they messed up on the naming. Java (and according to your comment, Dart) gets enum rights. What Rust has under this name is sum types, which is a separate (more expressive) concep…

Rust isn't alone though - Swift's `enum`s are essentially the same as Rust's enums.

Re: Flutter 3

#307

+1 for Flutter 3 supports the Apple Silicon Mac (aka M1). I could not get this to run on a Ubuntu VM (arm64) - anyone know if this is also working?

Works fine for me in Asahi Linux, both Flutter 2.x and after upgrading to 3.

Really using Asahi as a daily driver? Thought it didn't have video acceleration yet?

Re: Flutter 3

#308
post #269
post #250

Earlier quoted context omitted.

Former O'Reilly editor here: story checks out. The 1/3 might be a bit low -- I had some surprises (one guy joined the Peace Corps and moved to South America, plus usual divorces and deaths and job changes) but it felt more like 80% completed. This might be the rosy glasses of memory, though. There's also a weird difference in incentive between writing the first edition and working on updates: if the author was just a…

That is fascinating. As someone who has writing a technical book as a life goal, I'd love to ask--do you have any insights you'd be willing to share regarding how to get started?

Pick a topic you know a lot about, or are willing to learn a lot about. Start writing.

Re: Flutter 3

#309

Earlier quoted context omitted.

The way it atleast used to be framed is that web is a fallback target. Meaning if the target device isn't running Linux, Windows, macOS, iOS or Android (unlikely), then hey, you can atleast build a passable version that will run in a browser. I don't know if this has changed, but I know only a mad man would try to build a proper website in Flutter. It's not the tool for the job.

I’ve encountered a Flutter web app exactly once, https://app.travellerdeclaration.govt.nz/ . It was very painful. (Part of the pain was related to them using a selectable-button style for radio buttons, which isn’t entirely Flutter’s fault, though I bet it contributed to that misguided decision; but when there’s no scrollbar and the Yes/No button you clicked is at the very bottom of the visible page—well, that was th…

That was painful indeed! Why you would use Flutter for something that seems to be web-only, and on a govt website that presumably values accessibility, is beyond me.

Re: Flutter 3

#310
post #151

Earlier quoted context omitted.

I think the decision of which cross platform technology to use mostly depends on a team's preferred tech stack. C++ -> QT C#/.NET -> MAUI/Blazor JS/Web -> React.Native/Electron Dart -> Flutter This is what I think is holding back Flutter -- that it wasn't built on an incumbent technology. Because Dart doesn't have quite the following, it has to evangelize itself a bit more than the other options.

Rust -> ='[

https://iced.rs/
Post reply on HN