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

221–230 of 748 posts

Re: We're forking Flutter

#221

Post by Onavo »

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…

> Most people don't realize how many apps written in Flutter they use daily, simply because it's impossible to tell.

Flutter implemented its "native" looking UI widgets by literally having teams of designers eyeball the native designs and reimplementing, starting from drawPixel. This can't be done on a volunteer basis alone. Many open source attempts have tried this route and failed because they don't have the sheer designer resources needed to get there.

https://docs.flutter.dev/ui/widgets/cupertino

Re: We're forking Flutter

#222

Post by contextfree »

LordDragonfang wrote: post #160
1propionyl wrote: post #134

Earlier quoted context omitted.

Flutter is really not some big revelation and it's always shocking to me how it's evangelists act like it's the game changer no one else has noticed. It's just not that good? Just build native UIs. I don't know why cross platform UI has been such a hobbyhorse for so many for so long: it's a stupid idea.

As someone desperately fighting to keep their company's main product to stay using a native desktop UI, Microsoft makes it real hard. WinUI3 hasn't even officially launched and it already feels like it's on life support. QT is good, but even qt seems to be starting to use a web renderer.

"WinUI3 hasn't even officially launched"

? It officially launched with version 1.0 and it's now on 1.6?

Re: We're forking Flutter

#223

Post by pzo »

irq-1 wrote: post #202
pzo wrote: post #128

Earlier quoted context omitted.

> Also frankly, nobody forking Flutter will be nearly skilled enough to work on the Flutter engine (Impeller). For me its so weird they ditched google/skia to develop Impeller in Dart from scratch in the first place. If skia was not ready they could move just 1-2 developers to Skia team to collaborate with them. Now they want to even write their own 3d rendering lib based on Impeller (flutter_gpu, flutter_scene) even…

The build process for skia and its dependencies is huge. Flutter compiles (on windows) with CMake and Skia uses googles GN tool. https://skia.org/docs/user/build/ https://gn.googlesource.com/gn

They been building it before and still building and releasing with flutter so it's not like they don't have pipeline for that. And it was distributed compiled so nothing to compile for 3rd party users.

Re: We're forking Flutter

#224

Post by mdhb »

1propionyl wrote: post #157
mdhb wrote: post #151

Earlier quoted context omitted.

Back in the real world however you have canonical for years now who have made flutter the default for all native linux desktop development. I think your anecdotes are a bit out of date and irrelevant. People much better informed than you looked at this problem in a lot more detail in real life situations and came to very different conclusions.

> you have canonical for years now who have made flutter the default for all native linux desktop development And yet, I can't think of a single app I depend on for anything on Linux that relies on it. How'd Snap go for Canonical?

Cool, none of that is remotely relevant to what we are talking about here.

Your anecdotes are dated and you should think about updating them so you don’t talk so confidently on things you don’t actually seem to know much about.

I mean that sincerely not as some internet gotcha there’s just no need to sit there defending a position that is based on old info just for the sake of it.

Re: We're forking Flutter

#225

Post by kernal »

mvac wrote: post #4

Very sad article to read. I just expect the original Flutter will now die a slow death. I applaud the effort and hope they will be able to find a monetization model that works to support the development. There have been similar projects based on technologies that Microsoft has killed (Silverlight -> OpenSilver and various .NET-based cross-platform technologies) that serve their customers well. Unfortunately, none of…

>Very sad article to read. I just expect the original Flutter will now die a slow death.

I find it odd that you would think this fork would even have an impact on Flutter or its roadmap.

Re: We're forking Flutter

#226

Post by veeti »

ko27 wrote: post #74
normie3000 wrote: post #19

Earlier quoted context omitted.

> Flutter is truly a piece of great tech with remarkable quality and value. How does it compare to React Native from user and developer experience perspectives? Are there other competitors?

It's better in most ways, for example, just recently LG decided to rewrite its TV apps from RN to Flutter https://webostv.developer.lge.com/news/2024-07-15-new-and-su... > Most of our apps use React. When we first adopted React, we were pleased with the development productivity it provided, but sadly its initial performance was subpar in terms of start-up time, memory consumption, and responsiveness. After significan…

Not familiar with webOS, but are they talking about React Native specifically or just "web" stack React?

Re: We're forking Flutter

#227

Post by divan »

kernal wrote: post #184
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…

>Flutter is the best thing that happened to UI development since Qt. Most people don't realize how many apps written in Flutter they use daily, simply because it's impossible to tell I agree with you that Flutter has been a boon for cross platform development, but to say it's impossible to tell you're using a Flutter app is a bit of an exaggeration. I have no problem identifying Flutter apps. Not that I care as they…

How do you do that? I just opened my phone, and the last app I used was a food delivery app. How can I figure out if it's a Flutter app or a native one?

Re: We're forking Flutter

#228

Post by synergy20 »

This is a welcome fork. Still for me, flutter is not web platform friendly by design(e.g. javascript) and that's the reason I stopped using it and switched to react-native + electronjs(react), they seem more reliable and production ready, plus this approach is totally web friendly.

Re: We're forking Flutter

#229

Post by criddell »

droideqa wrote: post #85
giancarlostoro wrote: post #70

Earlier quoted context omitted.

WhatsApp had less than 50 engineers (or was it employees total?) when Facebook bought them out, and they had millions of users.

The power of Erlang.

Since Instagram had only 13 employees when Facebook bought them for $1 billion, does that mean:

    power(Python) > power(Erlang)?

Re: We're forking Flutter

#230

Post by hadad »

ko27 wrote: post #74
normie3000 wrote: post #19

Earlier quoted context omitted.

> Flutter is truly a piece of great tech with remarkable quality and value. How does it compare to React Native from user and developer experience perspectives? Are there other competitors?

It's better in most ways, for example, just recently LG decided to rewrite its TV apps from RN to Flutter https://webostv.developer.lge.com/news/2024-07-15-new-and-su... > Most of our apps use React. When we first adopted React, we were pleased with the development productivity it provided, but sadly its initial performance was subpar in terms of start-up time, memory consumption, and responsiveness. After significan…

Misleading on the comment, LG WebOS is using EnactJS (Framework on top of ReactJS) + Chromium Embedded Browser, not native, just webapp on browser.

But React Native is different , JS code compiled to native code using c/c++ compiler on target system. Flutter also do like this one.

Embedded browser is slower than native app, because extra browser layer than native one.

Post reply on HN