Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Flutter 2

developers.googleblog.com

Post reply on HN
Print view View original

431–440 of 780 posts

Re: Flutter 2

#431

Post by e12e »

randomchars wrote: post #35

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. […

I'm seriously considering looking at something like https://heaps.io/ for cross platform utilities rather than flutter etc. i suppose accessability is likely to still be an issue, as well as ciustom (not native) widgets -but at least the resource usage and interaction is likely to work?

note that heap+haxe is pretty much "the same" as flutter/dart - a language, a compiler and a runtime + a rendering engine..

Re: Flutter 2

#432

Post by Hixie »

xvilka wrote: post #400
reader_mode wrote: post #316

I'm currently 5 months into developing a mobile app for a startup with flutter and my experience so far is very underwhelming. Flutter as a framework is not the worst but far from best, it's very OO while trying to use reacts vdom model which just wants to be functional. The biggest limitation of the platform is Dart - it's a horrible language that should have died once TS and ES6 became mature enough. And I've used…

Would have been be nice if they provided a way to use Kotlin Native as a language for Flutter instead. Not a JVM Kotlin of course, because it's too slow for the native mobile apps. Or, even better, Rust. That would be very impressive.

If you prefer Kotlin you may find https://developer.android.com/jetpack/compose more to your tastes.

Re: Flutter 2

#433

Post by meibo »

timgilbert wrote: post #159
meibo wrote: post #44

Earlier quoted context omitted.

Stadia isn't cancelled. The studio is. Stadia itself won't go away any time soon.

Indeed, looks like it's got 989 days remaining. http://stadiacountdown.com/

If you'd have any clue of the games industry, you wouldn't be saying this.

AAA publishers are pushing heavily for this since it makes piracy and hacking obsolete and they always get what they want - there's no way that this is not the future of "popular" gaming.

Re: Flutter 2

#434

Post by okamiueru »

oblio wrote: post #384
okamiueru wrote: post #307

Earlier quoted context omitted.

You could create an abstract class for the base response, then implement this abstract class for the two cases one where it has a list member, and one where it contains the object. Then, using the return value with something like `if (response is listLike) { }` the IDE already knows that you are scoped to having only the list like properties, and you'd get the full help of the language. Something like that, I suppose…

Versus a sort of: my_type = my_list | my_object ? You can see why this is better :-)

All I can say is that it is certainly neat :)

Re: Flutter 2

#435

Post by Hixie »

SamBam wrote: post #290
fastball wrote: post #211

Earlier quoted context omitted.

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

It takes work to make it non-selectable. In Flutter, it defaults to non-selectable. Most of the time a dev isn't thinking "I'd better make this selectable," because they simply aren't going to think of all the reasons someone might select text. They'll think of the obvious-to-them cases, and leave all the other text as unselectable.

It doesn't really default to anything. There's a widget for selectable text and a widget for non-selectable text.

Re: Flutter 2

#436

Post by ryandrake »

hanniabu wrote: post #301
blacktriangle wrote: post #132

Earlier quoted context omitted.

We're nagging because the apps suck and stick out like a sore thumb. Maybe Flutter will be the one to get there and be the holy grail of cross platform UI development, but the developer community has been burned by this promise so many times, we're going to have to see the final product before getting excited. Just because a project is ambitious doesn't mean we should all jump on board, particularly when similar proj…

I don't understand why more resources aren't being put into Qt and making that easier to use or building a more "web-developer-friendly" abstraction layer on top.

I don't even fully understand why "cross-platform UI development" is such a holy grail. Is it that expensive to separate your business logic from UI and write the small UI layer in whatever the platform's "best practice" native language is? Is it that hard to find developers who know more than one programming language? With a lot of these frameworks and higher level abstractions, if you go off the toy-app happy path, you end up fighting the framework and tools more than you're writing your app anyway.

Re: Flutter 2

#437

Post by MongooseMan »

distances wrote: post #407
jamil7 wrote: post #348

Earlier quoted context omitted.

Yeah but it’s usefulness is really limited and just feels shoehorned into the project. Why couldn’t it have been Kotlin or TS? Something that mobile developers or web developers could jump into and keep a bunch of their existing tooling.

Then you would've needed to package a JVM or a JavaScript engine, making the app distribution a whole lotta different deal.

Kotlin doesn't just run on the JVM - it can compile to native binaries with Kotlin Native. It compiles to WASM and JS too.

Re: Flutter 2

#438

Post by marcusjt »

eseidelGoogle wrote: post #98
sydd wrote: post #87

Earlier quoted context omitted.

I've tested on my phone (1yr old pretty good Android one) and the whole thing is very laggy runs with like 10fps. What about a11y? The whole thing feels like Adobe Flex in 2010. It solves a great deal of problems that the web had but introduced a plethora of others.

[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.

FWIW the plasma demo runs at something like 50fps in Chrome on my 3yr old Samsung Galaxy S9, and only a bit worse in Firefox (perhaps 40fps) - so they are not buttery smooth experiences, but neither are they terrible.

Re: Flutter 2

#439

Post by K0nserv »

whymarrh wrote: post #83
dstaley wrote: post #7

Flutter for Web feels like such a wild step backwards in terms of functionality that I'm not sure the benefits it brings are worth it. I just tried a few samples, and basic interactions like selecting text, saving images, and opening links in new tabs don't work. This is the result of rendering everything to a element. I'm much more interested in a React Native style approach, which seems to provide a consistent set…

> This is the result of rendering everything to a element. If the accessibility story isn't rock-solid, frankly this is a non-starter for a lot of applications. Web apps suck in a lot of ways but regular HTML has pretty great accessibility properties.

It is far from rock-solid. It's shockingly bad in fact.

Re: Flutter 2

#440

Post by gagege »

danShumway wrote: post #360
hanniabu wrote: post #301

Earlier quoted context omitted.

I don't understand why more resources aren't being put into Qt and making that easier to use or building a more "web-developer-friendly" abstraction layer on top.

I don't know if they've changed their approach over the past year, but the last time I looked at Qt demos for the web, I was solidly unimpressed. At the time, they were making almost all of the same mistakes that Flutter is, and the devs I talked to seemed to be of the opinion that those problems wouldn't be fixed until browsers started adding brand new capabilities specifically for them. Looking now at the demos at…

Whoa, yeah, none of those Qt demos are good or even seem to work properly. Yikes.
Post reply on HN