Live data from Hacker News

We're forking Flutter

flutterfoundation.dev

721–730 of 748 posts

Re: We're forking Flutter

#721

Earlier quoted context omitted.

I almost never use email on anything but my phone, and Gmail doesn't use a table. They do some tree stuff for the conversation threads, but conversation threads are obnoxious anyway and I have no idea why anyone likes them, they don't reflect face to face conversations well and always create mistakes where someone forgets to reply to all. I've replaced a lot of tables in my apps with modal dialog UIs, it's nice to ha…

This is something I have a difficult time agreeing on. I expect a certain level of information density and configurability in desktop UIs, which shoehorned mobile-style UIs don't do well to provide. Deep modality is also a peeve; on desktop there's often no benefit to burying things in mulitple layers of modals — within reason, the most important things should never be more than one click away and great consideration…

There's a number of users who can really make great use of the power user tools, but adding multiple UI options can greatly increase work, because a fully modal workflow might need a completely different frontend, and some apps are meant for the mass market.

Degrading the experience for the majority just to make things better for the power users doesn't seem like it's always the best plan unless you're specifically targeting power users.

In the extreme case, UI for power users can result in production databases being destroyed, or someone getting served food allergens because the menu system made it easy to assign wrong items to wrong customers, or someone's entire family photo collection getting deleted by a single command.

Re: We're forking Flutter

#722
post #534

Earlier quoted context omitted.

So, basically: Python is performant when you don't use Python?

Yes. Is that so weird? JS is also performant when you don’t use JS considering you’re running it on C or Rust and are likely using the FFI if you’re doing any form of computation heavy work.

Yes, it's very weird. When I write JavaScript, I expect it to run reasonably fast because of the JIT - and it does. I've never felt the need to use FFI, and libraries that use it generally do so because they want to interact with pre-existing C or C++ code, not because it's the only way to get decent performance.

Re: We're forking Flutter

#723

Earlier quoted context omitted.

on behalf of one of the Flutter founders, thank you for the thank yous. I bet they'd mean a bit more if it wasn't coupled to a lengthy thinking-out-loud post that casts doubt on it, based on how many job listings you see, for something you don't look for job listings for. Quick Google shows Dart 10th, right below SQL, right above Kotlin. https://www.devjobsscanner.com/blog/top-8-most-demanded-prog...

> I bet they'd mean a bit more if it wasn't coupled to a lengthy thinking-out-loud post that casts doubt on it, based on how many job listings you see, for something you don't look for job listings for. Did you really just thank the guy for saying thanks, but give him a big fuck you in the same breath for not being a 100% kool-aid drinker? Speechless.

No, I sarcastically thanked him for free-association about the # of job listings he sees for job listings he's not looking for and what that means about the language.

I'm guess I'm capable of being curious and engaging in conversation, beyond sitting in the bleachers grading everyone on my scale that at 100% is "koolaid drinker.", depending on if I feel like the things they're talking about are on Team A or Team B I've identified.

Then again, that perspective would sort of come naturally if I were reading hysterics into every comment I read. "Big fuck you" is textbook catastrophizing.

Re: We're forking Flutter

#724
post #703

Earlier quoted context omitted.

Thats an excellent summary, and its fair for you to assume that question has been settled.

(On a serious note), inside Google you tend to get more easily promoted if you launch new products than if you maintain existing products, so it could be tempting for the employees themselves to follow in that direction.

Oh I'm aware (deep foreboding sad voice)

Re: We're forking Flutter

#725

While surfing around the various repos, I was reminded about the bad taste I got from the last time someone sung the praises of Flutter/Dart; this thing is firmly in the "Android SDK-ish" school of thought: download a shitload of prebuilt binaries from storage.googleapis.com, dontyouworryaboutit $ curl -I https://storage.googleapis.com/flutter_infra_release/releases/stable/macos/flutter_macos_3.24.4-stable.zip

Almost everything these days is installed like that.

Re: We're forking Flutter

#726

The thing I dislike about Dart and some other language like Swift or Ruby is that they only have one application. With Dart you write Flutter aps. With Swift you write iOS apps. With Ruby you write Rails apps. Java, C#, Rust, C, C++, Go, Python are usable for more than one thing. I am not saying Dart and Flutter aren't nice, but for sure I would love to see Dart extending to more than just Flutter and making Dart usa…

C# port of Flutter would be a dream.

C# has Maui for mobile and desktop development. And Blazor for fronted.

The community is oriented towards having one framework or library for doing one thing.

Re: We're forking Flutter

#728
post #622

Earlier quoted context omitted.

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

It's not specific nor limited to javascript. The term "canvas" in this context is much older and seems to be used across many platforms. Random examples from the (desktop) Java/Android/iOS world where the same semantics is used: https://docs.oracle.com/javase/8/docs/api/java/awt/Canvas.ht... https://developer.android.com/reference/android/graphics/Can... https://developer.apple.com/documentation/SwiftUI/Canvas

You may notice that the first reference is from java, and i bet js lifted it from there. They may have been aware of java because they lifted the name too.

The other two are too new to be relevant.

Re: We're forking Flutter

#729
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…

Besides, it's pure speculation; where's the hard data behind 1.000.000 developers? That's a very large number to be a guess.

Re: We're forking Flutter

#730

so we cant sent a pr to flutter or what? I always thought flutter is open source

> I always thought flutter is open source

It is, this has nothing to do with that. The argument here is that PRs doesn't get merged easily, which Flock want to ease on

Post reply on HN