Who is "we" in all of this?
Not even visible on the github org https://github.com/Flutter-Foundation
> This organization has no public members. You must be a member to see who’s a part of this organization.
We're forking Flutter
291–300 of 748 posts
Re: We're forking Flutter
#292Earlier quoted context omitted.
I would consider both GTK and Qt native on Linux.
So that means one has to target both GTK and Qt to be native on Linux. Fat chance of that on anything but yet another music player or other relatively trivial UI app. In any event, that still doesn't answer what it means to be "native"? And my point is I think most definitions are dumb or useless. If I'm running a GTK desktop, Qt apps are generally not "native" no matter how much theme fuckery one tries. Native can a…
> So that means one has to target both GTK and Qt to be native on Linux.
Doesn't it mean that you can target _either_ and be considered native?
Also, I'm not sure I buy the claim that of "GTK and Qt are native" in the first place. I'd say either that there is no native UI, or if I must call something native, it's the toolkit the desktop environment uses. And yes, that does mean that there is no "Linux nativeness" like there is Windows nativeness, as every DE is different. And rightly so, because one could in principle write a different DE over the Windows kernel, whose UI would behave differently.
Re: We're forking Flutter
#293Earlier quoted context omitted.
> Most people don't realize how many apps written in Flutter they use daily, simply because it's impossible to tell You can't be serious. Maybe on Android, but on other platforms—especially iOS—they stick out like a sore thumb. A number of them just look like Material Design Android apps awkwardly transplanted over, but I know that's down to the developer so I won't hold that against Flutter. But scrolling through th…
> but they don't fit in. You seem to say this like it's a bad thing?
I think it is, personally. Mostly because common UI appearance and paradigms makes software easier to use, especially for non-technical users.
But in this specific instance I was referring to OP’s claim that it’s impossible to identify many Flutter apps, which I dispute.
Re: We're forking Flutter
#294Back when I worked on GWT, we had trouble accepting outside contributions because the team had a mandate to support Googlers. That is, much like other libraries and tools at Google, changes could not break google3. This means testing patches against google3 and either changing the patch, or fixing whatever code used it, and these are tasks that no outsider can do. Shepherding these patches is no fun when you have you…
Couldn't flutter work as public-first that then gets vendored into third_party? Or is that literally the fork strategy you are talking about that I'm too dense to understand?
Yeah, that's what I meant. Public-first is good in some ways, but it means some bugs might be discovered rather late.
Re: We're forking Flutter
#295Earlier quoted context omitted.
Can’t, but not sure why that’s hard to believe?
Because billions of people or their devices aren't even online every hour. Unless you're discussing background processes on google's side
There are roughly 5 billion smartphone users now, those devices are almost always on and sending background data somewhere. By volume, more of that data guess to Google than anybody else, on the order of hundreds of network requests per device, per hour.
Re: We're forking Flutter
#296Guess Flock is free to use now that Google abandoned their other project named “FLoC”
Re: We're forking Flutter
#297Earlier quoted context omitted.
> Most people don't realize how many apps written in Flutter they use daily, simply because it's impossible to tell You can't be serious. Maybe on Android, but on other platforms—especially iOS—they stick out like a sore thumb. A number of them just look like Material Design Android apps awkwardly transplanted over, but I know that's down to the developer so I won't hold that against Flutter. But scrolling through th…
Sure, but not every cross-platform app developer wants their app to look "native to iOS". Especially if you want your app to look the same on all platforms and/or have some creative design.
In those cases, those app developers aren't doing cross-platform development, but are just trying to dump their app in as many places as possible. In such a case, why not just make a PWA and call it a day? Don't need an app if you aren't going to go native, especially with most apps being either content readers or CRUD apps anyway.
In most cases, I personally rarely want an app, and I'll use a website unless they happen to have created a great native experience. And since most apps don't, I don't use them, and I don't have a lot of apps as a result.
Re: We're forking Flutter
#298Earlier quoted context omitted.
Exaggeration? Billions per HOUR seems quite a stretch there..
I believe it. I've never worked at Google, but I was the engineer for SMS/Voice registration at WhatsApp, ocassionally with one other engineer (I believe the team was 3 when I left, not sure if it grew); I think there were two engineers doing my job for Facebook; although they had a little bit more scope, since there were more kinds of SMS they sent. That doesn't have a huge request rate, but it is super important. S…
Exactly, there’s really like three dozen or so people globally who really should never be in the same room at the same time as the risk is too great they get hit by the same asteroid.
I’d put “person who makes sure WhatsApp verification codes work” on that list.
Re: We're forking Flutter
#299Earlier quoted context omitted.
WhatsApp has a very narrow use case and feature set to support. Flutter is a multi-platform framework for developing apps like WhatsApp. It seems like a apples and oranges here.
What about Python? They had 34 core developers in 2017 [0]. Python is used by millions of devs. They have to support a multitude of platforms as well. Same goes for a lot of programming languages like Go: a pretty small core, the rest is external contributions. And they have to support all sorts of platforms/configurations as well (probably more than Flutter does). [0] https://pythondev.readthedocs.io/core_devs.html
As core languages, the scope of both Python and Go is fairly well defined.
Re: We're forking Flutter
#300Earlier quoted context omitted.
50 people is a pretty huge team at Google to start with, there’s teams of <5 that support weird bits of core infrastructure that serve billions of users an hour.
Exaggeration? Billions per HOUR seems quite a stretch there..
World population is 8.2 billion. Assume that 1/3 are asleep at any given time, leaving 5.5 billion awake. It’s not a huge stretch to imagine 20% of them (1.1 billion) using core Google services during peak times.