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

We're forking Flutter

flutterfoundation.dev

Post reply on HN
Print view View original

401–410 of 748 posts

Re: We're forking Flutter

#401

Post by dekhn »

yonran wrote: post #352
odo1242 wrote: post #117

Earlier quoted context omitted.

What is google3?

Here is a paper describing google3 https://research.google/pubs/why-google-stores-billions-of-l... , which includes the policy that “To prevent dependency conflicts, as outlined earlier, it is important that only one version of an open source project be available at any given time.” More documentation on The One Version Rule for third_party: https://opensource.google/documentation/reference/thirdparty... . This rule…

I used to maintain the internal (single) version of numpy and scipy and honestly I think the one-version rule was awesome. It greatly reduced noise and churn. It meant far less breakage, and it was easy to find and fix all the breaking tests when I was updating to a new version. I guess the only downside is sometimes an older version of numpy would prevent deepmind from making some sort of ML advance until I upgraded to get some new feature they wanted.

Re: We're forking Flutter

#402

Post by [deleted] »

FredPret wrote: post #394
brainless wrote: post #391

Earlier quoted context omitted.

Python doesn't have a narrow scope. At least compared to Flutter. It's in so many places, from Linux installers, to medical, aerospace, math,... and finally the web (which is probably what we hear about the most).

But those are modules added on by developers other than the 50 core devs.

[deleted]

Re: We're forking Flutter

#403

Post by lolinder »

FredPret wrote: post #394
brainless wrote: post #391

Earlier quoted context omitted.

Python doesn't have a narrow scope. At least compared to Flutter. It's in so many places, from Linux installers, to medical, aerospace, math,... and finally the web (which is probably what we hear about the most).

But those are modules added on by developers other than the 50 core devs.

The standard library alone has a huge scope which includes a (mediocre) GUI toolkit.

Re: We're forking Flutter

#405

Post by epcoa »

dotancohen wrote: post #377
epcoa wrote: post #242

Earlier quoted context omitted.

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. Incorrect. Target one or the other, not both.

How is Qt within a GNOME or Xfce environment any more "native" than Qt on Windows or Mac?

You have reduced the definition of "native" to merely compatible with X11/Wayland (that's the only common denominator). Well now, Tk, FLTK, Swing, and even Wine are all native.

Re: We're forking Flutter

#406

Post by WD-42 »

FredPret wrote: post #394
brainless wrote: post #391

Earlier quoted context omitted.

Python doesn't have a narrow scope. At least compared to Flutter. It's in so many places, from Linux installers, to medical, aerospace, math,... and finally the web (which is probably what we hear about the most).

But those are modules added on by developers other than the 50 core devs.

Have you seen the python standard library? It ain't JavaScript kiddo

Re: We're forking Flutter

#407

Post by alberth »

1st1 wrote: post #348

> How large is the Flutter team, today? Google doesn't publish this information, but my guess is that the team is about 50 people strong. > That's 50 people serving the needs of 1,000,000. Doing a little bit of division, that means that every single member of the Flutter team is responsible for the needs of 20,000 Flutter developers! That ratio is clearly unworkable for any semblance of customer support. This is a we…

Rails has 12 core developers + 5 committers.

https://rubyonrails.org/community

Re: We're forking Flutter

#408

Post by kllrnohj »

rvnx wrote: post #368
1st1 wrote: post #348

> How large is the Flutter team, today? Google doesn't publish this information, but my guess is that the team is about 50 people strong. > That's 50 people serving the needs of 1,000,000. Doing a little bit of division, that means that every single member of the Flutter team is responsible for the needs of 20,000 Flutter developers! That ratio is clearly unworkable for any semblance of customer support. This is a we…

“Flutter team members don't actually use Flutter.” (as per the website). This could explain a lot.

Very rarely do the people working full time on a framework/tool also use that framework/tool in a non-toy setting. They aren't working two full time jobs after all.

Re: We're forking Flutter

#409

Post by loic-sharma »

jwells89 wrote: post #314
divan wrote: post #120

> We describe Flock as "Flutter+". In other words, we do not want, or intend, to fork the Flutter community. Flock will remain constantly up to date with Flutter. That was the first fear when I saw the title - splitting community and having two incompatible versions. Good to see it addressed in the post. The second was just a fear of how it would complicate the development process, but it seems to be a drop-in replac…

I can’t imagine using Flutter for desktop development if only because like most newer UI frameworks, it’s mobile focused and doesn’t come with important desktop widgets like tableviews/datagrids and treeviews.

two_dimensional_scrollables is a first-party package by the Flutter team that implements table views and tree views: https://pub.dev/packages/two_dimensional_scrollables

Re: We're forking Flutter

#410

Post by dietr1ch »

lolinder wrote: post #403
FredPret wrote: post #394

Earlier quoted context omitted.

But those are modules added on by developers other than the 50 core devs.

The standard library alone has a huge scope which includes a (mediocre) GUI toolkit.

I did not meant to start a pissing contest, I thought the biggest idea was that Flutter isn't 35yo and because of it, it's more likely to drastically change, and in a fast way too.
Post reply on HN