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

581–590 of 748 posts

Re: We're forking Flutter

#581

Post by dominicrose »

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…

After using Typescript and React, building a front-end with Flutter is boring, as are other Google frameworks (Angular, GWT).

Maybe if you've never worked with TS/React and more generally HTML/JS/CSS, then it may be OK for some use-cases.

Re: We're forking Flutter

#582

Post by Alifatisk »

The most important thing I wish this doesn't cause is to divide the community, but the article addresses this.

I enjoy Flutter a lot, it would be very sad if it got discontinued. An previous employee at Flutter just showcased how powerful the framework can be outside it's main usage. https://www.youtube.com/watch?v=fU6d81MurTQ

Re: We're forking Flutter

#583

Post by ForHackernews »

divan wrote: post #576
ForHackernews wrote: post #568

Earlier quoted context omitted.

> But when you actually think about it, it's an insanely stupid UI choice that neither of proper UI frameworks would even consider. You say "insanely stupid", I say wonderful. Everything you apparently hate about the web is what makes it good for users. Content is primary, and my user agent can resize it, restyle it, copy it, extract it, link it, read it to a blind person... If you want to make a binary blob app, jus…

> You say "insanely stupid", I say wonderful. Yes, that's the most common response. I've heard stories about "how wonderful when you can select everything" multiple times, and that's, of course, just shows how human rationalization works. And yet, this "feature" or "UI choice" is not even a choice. It's just a byproduct of using the wrong stack for the task. Like, nobody ever sat and asked, "Do we want our apps to ha…

It didn't "just happen" the early architects of the web designed a system to make it easy to share and remix content and subsequent generations of companies and their UX designers have so far failed to fully claw back user freedoms.

Re: We're forking Flutter

#584

Post by madeofpalk »

divan wrote: post #547
madeofpalk wrote: post #384

Earlier quoted context omitted.

What are some examples of good 'impossible to tell' UIs built with flutter on desktop or web?

My comment was related to mobile apps. Web apps built on Flutter definitely can be distinguished. The thing is, with web apps, people have developed feelings for the "nativeness" - because browsers make a lot of UI choices for them. A typical example is a selection of the text. Because web apps are built using XML-based typesetting language from 80-s, everything is selectable by default. No matter how many layers of…

What are some examples of good 'impossible to tell' UIs built with flutter on mobile?

Re: We're forking Flutter

#585

Post by EdwardDiego »

wiseowise wrote: post #496
Capricorn2481 wrote: post #476

Earlier quoted context omitted.

Just seems like personal preferences. I've used languages with extensive pattern matching and don't feel like I'm missing out without them. Don't really see the problem with Gradle or Static Delegation either.

Then you won’t understand what made Flutter “click”. I work with Kotlin, Gradle and Compose on a day to day job and it is absolutely dreadful experience. Sure, it beats working with Java… Java 8.

Thanks for explaining your stance not a whit.

I was genuinely interested in your thoughts, "you wouldn't understand it, but trust me" is deeply unhelpful.

Re: We're forking Flutter

#586

Post by evomassiny »

eseidel wrote: post #51
Topfi wrote: post #20

As someone reliant on Flutter, it is likely better to rip off the band-aid now than wait for a slow, prolonged decline. That being said, whilst I am at least somewhat comforted that the person taking charge is someone who was involved with the Flutter team at Google in the past, rather than a random, overenthusiastic person, I have a few crucial criticisms on this post that make me skeptical. For one, I'd recommend a…

Flutter Founder here. If you ever have any concerns re: Flutter, please don't ever hesitate to reach out. eric@shorebird.dev

I've nothing to add to the conversation, but I jump on this oportinity to tell you that i like the content you've made with Adam Barth on yt very much, have a great day :)

Re: We're forking Flutter

#587

Post by 1oooqooq »

wruza wrote: post #456
1oooqooq wrote: post #439

Earlier quoted context omitted.

you know that zero texting apps nowadays use native input anyway right? even native apps will implement their own input and it's always awful, but the pm needs those style previews... (you're still right thought)

Checked my whatsapp and tg, both use absolutely native inputs. The selection handles & menu, the hold-spacebar movement, the hold-to-magnify feature on ios is the same as everywhere else. If that’s not native, they did a great job for nothing. Too lazy to check on android rn, but I recently worked with the apps/chats on it and entered text, it didn’t feel different.

it's not a native widget. you can type styles on whatsapp which is not possible on native input.

whatsapp is the poster child of this technique btw.

Re: We're forking Flutter

#588

Post by pzo »

xster wrote: post #170
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…

https://github.com/flutter/engine/blob/main/impeller/docs/fa... discusses the reasoning a bit. There's more of a difference in the approach

Related https://groups.google.com/g/skia-discuss/c/Fzpne-f9gZ4/m/5_I...

Seems like most issues could be solved with new Skia graphite backend

Re: We're forking Flutter

#589

Post by nottorp »

Nekit1234007 wrote: post #580
nottorp wrote: post #512

Earlier quoted context omitted.

> the underlying platform UX and draws to a canvas Frame buffer? Canvas is the javascript term.

Flutter uses canvas when targeting the web. (At least it was the last time I looked at it years ago)

Canvas is the javascript name for writing directly to a frame buffer :)

There is a world outside the browser. For now.

Re: We're forking Flutter

#590

Post by CJefferson »

satvikpendem wrote: post #536
CJefferson wrote: post #460

Earlier quoted context omitted.

Out of interest, do you know many seriously vision-impared people? Windows, and Mac OS X in particular, have quite good support for accessibility if you use their built-in GUI systems, and unified UIs are often (not always, vscode and chrome are quite good, for example), very bad, sometimes just a black square as far as accessibility goes.

Many cross platform frameworks have good accessibility support, not sure what that has to do with native platforms, as the cross platform solutions simply hook into the native platform accessibility APIs anyway. https://docs.flutter.dev/ui/accessibility-and-internationali...

I didn't know flutter had such good support, and I'm very happy to hear about it!

Unfortunately, most cross-platform frameworks have awful accessibility support, I've looked at various in the past and just found failure after failure. I am now going to look harder at flutter.

Post reply on HN