Live data from Hacker News

Google's cross-platform Flutter UI toolkit goes 1.0

techcrunch.com

241–250 of 343 posts

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

#241
post #123

Earlier quoted context omitted.

Which is irrelevant to my point, which is that it's also used where it's not native.

So Cocoa is missing from your list given iTunes on PC.

Given the usage of e.g. and offering the most charitable interpretation of coldtea’s comment, I guess it wasn’t supposed to be an exhaustive list, just the first (or most pervasive?) thing that came to mind.

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

#243

Earlier quoted context omitted.

What? Qt is mostly LGPL. You don't need a lawyer.

Try to download it from qt.io. You will have to go through several screens saying "Are you sure you are able to comply with the LGPL? Wouldn't you rather get the commercial version for peace of mind?". If that isn't an implied threat, i don't know what is.

I don't approve of that tactic (in fact it drives me nuts), but I will say, Qt's license fees are quite reasonable, and then you get to link statically with no risk of violating the GPL.

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

#244

Earlier quoted context omitted.

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.

[deleted]

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

#245
post #23

Google has a history of introducing products and then killing them. For developing mobile apps they currently support "vendor native" via Android Studio using Java or Kotlin, Progressive Web Apps, and now Flutter. Will Google really support all three over the long term?

What you think they want to let Facebook control mobile development?

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

#247
post #204

Earlier quoted context omitted.

There's one place where none of this matters: Games engines. Games have the same, consistent (hopefully) easy to use interface across every platform they support. They either accomplish this, or they simply don't survive on the market. It has to be said that most modern UI frameworks ARE game engines, anyway. Or maybe its a tautology: game engines eventually become platforms, which become "OS's on other OS's". Which…

Game engines are a place where it makes sense to roll your own UI framework many times, so on that point I agree with you. The purpose of a game is generally immersion and escape, so makes sense to remove users from their device's UI in many instances. Game UIs tend to have their own conventions so frequent players don't have much of a learning curve. But in general players accept some learning curve because games ar…

What sort of "other purposes" would it serve for the UX to be worse? Do you have any IRL examples of this happening?

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

#248
post #212

Earlier quoted context omitted.

It depends on what you mean by best. For us, we want to use the web stack so our stuff works across all platforms. So we use Cordova. We realize that over 90% of users just want to use the main interface and not some fancy OS feature. All our effort goes into making the product rock solid stable, engaging and easy to use. We aren’t actually interested in making it feel exactly like a native iOS or Android app.

Well, such things are causing subtle annoyance for users. This works as long as the value you provide is good, but the more and app is just a bad we view the more likely it becomes that people uninstall it or look for alternatives. Unsurprising consistent behavior is a value.

> Unsurprising consistent behavior is a value.

Looking at the last 30 years of software development, it's pretty clear that users don't care very much.

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

#249

Earlier quoted context omitted.

I haven't touched Android development since 2012. I remember the experience being a terrible hodge-podge of XML and Java which effectively required an absolutely attrocious IDE and an impossibly slow emulator. I assume things have changed since then, but I wonder by how much and if Flutter's workflow skirts any of these issues altogether.

> I assume things have changed since then Yes, tremendously so. It's still XML for basic UI, but Kotlin is the primary language of choice these days, Android Studio is a solidly world-class IDE, and the emulator is very fast. > but I wonder by how much and if Flutter's workflow skirts any of these issues altogether. Flutter uses the regular Android emulator, and although you have more editor choice the recommended wa…

Is there any alternative to XML? How often do you find yourself hacking XML directly?

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

#250
post #44

Earlier quoted context omitted.

That's what I thought about Tcl/Tk.

Tcl/Tk is 30 years old. I would be willing to bet my retirement that none of the now-popular presentation technologies will be mainstream 30 years from now. They just don't have that kind of shelf life. If Flutter lasts a decade, it will have lived gloriously. React should be so lucky.

> I would be willing to bet my retirement that none of the now-popular presentation technologies will be mainstream 30 years from now

X-Windows? That thing started life more than 30 years ago, and still going strong on Linux.

Post reply on HN