Live data from Hacker News

Flutter desktop isn’t there yet

plei.one

181–190 of 242 posts

Re: Flutter desktop isn’t there yet

#181

Not surprising. Here's my quick criteria for whether I should use a new framework for my app: - look at other apps that are using that framework, esp. the signature/first class app touted as a consumer by that framework - how similar is my app to that signature/first class app? - if my app has similar UX/UI usage then the dev experience will be much smoother/easier/doable i.e. for React Native: does my app behave lik…

This is exactly why even after I made the decision, I’m still somewhat hesitant on learning Django. With RoR it’s a different story, but Django is a bit weird in this regard (users, references, popular applications).

Re: Flutter desktop isn’t there yet

#182

Not surprising. Here's my quick criteria for whether I should use a new framework for my app: - look at other apps that are using that framework, esp. the signature/first class app touted as a consumer by that framework - how similar is my app to that signature/first class app? - if my app has similar UX/UI usage then the dev experience will be much smoother/easier/doable i.e. for React Native: does my app behave lik…

Probably this one https://rive.app/

Re: Flutter desktop isn’t there yet

#183

Earlier quoted context omitted.

CLAs are always a good idea if one is maintaining an open source project. I'm not going to track down every single contributor who made some small PR perhaps, just to make a license change.

Why is your project changing the license, and why do you assume that contributors would still have done so under whatever license you're changing to?

The license could change for any number of reasons, making a paid version, making it GPL, etc. With a CLA, I don't have to assume, I'm able to change it regardless, that's why for maintainers they are useful.

Re: Flutter desktop isn’t there yet

#184

Earlier quoted context omitted.

I’m not sure why the Dart hate honestly. It’s a pretty solid language in my opinion and I like the direction they’re taking (non-nullable, record, pattern matching). The ecosystem is weak for sure, but that’s not a gripe on the language itself. I’m curious what do you dislike about it apart from semi-colons and the constructor syntax (which seem fine to me?).

Last I checked you can’t even have enums with payloads/ associated values. Garbage language

You can since 2.17. Not sure if you’re being sarcastic about this making it a garbage language.

Re: Flutter desktop isn’t there yet

#185
post #174

Earlier quoted context omitted.

For example, making an AOT compiler. Or adding other features. Or making the implementation more suited to client side apps. There are many things you can do to a language to make it easier for a specific use case. In the extreme, this is what DSLs are. I don't understand why you don't understand that having first class control over a language's development is a useful thing to have.

Useful? Maybe. Yet you didn’t give any language feature not found in literally any other managed language.

All else being equal, it is still useful to have control over a language's development. It doesn't matter that Dart may or may not have features not present in other languages, as long as they can add them as necessary based on Flutter's development.

Re: Flutter desktop isn’t there yet

#186
post #17

The more "solutions" that are developed for desktop + mobile cross-platform applications, the more I see highlighted how different the paradigms are, and how the streams really shouldn't be crossed. They're both UIs viewed on a screen that you interact with by pointing and clicking, but the similarities end there. The entire output of this cross-platform effort has been awkward applications that run everywhere but fe…

I wonder how many people Maxis employed when they made Sim City 2000? Because it had a native UI for every platform it was ported to that had a windowing and widget toolkit.

I just can't help but think that either programmers today have abstracted themselves into a lot more work than need to do, or they're just significantly less capable over all than the programmers of old.

Re: Flutter desktop isn’t there yet

#187

Hello, I'm from the Flutter desktop team. Thank you for the excellent feedback, this is truly invaluable. Here are some updates from our side: 1. Custom context menus - We just added this feature in Flutter 3.7, which was released two weeks ago. Please give this a try and let us know what you think! 2. Multi-window - This is a high priority for the Flutter team, we have several engineers working on this project curre…

Hi! I was wondering about the coexistence of Flutter and Kotlin in Android development. Is there any good write-up to help devs to choose between them depending on the use case?

Not who you want an answer from but for me if I was writing an android only app I'd go for kotlin, if I wanted android, iOS, desktop, and web I'd go dart/flutter.

Re: Flutter desktop isn’t there yet

#188
post #64

Earlier quoted context omitted.

Is impeler going to affect (in good way) the performance/latency on desktop too? (I think it's mostly for iOS now, right)?

Yup, but we're focused on mobile first as these are the most resource constrained platforms. We're also experimenting with 3D support in Flutter using Impeller. Check out these demos from Flutter Forward: https://youtu.be/zKQYGKAe5W8?t=6955 You can learn more about Impeller here: https://www.youtube.com/watch?v=gKrYWC_SDxQ

Something being highlighted about Flutter is that it ultimately compiles to native code so unlike RN which transpiles to native widgets, its UI animations should technically be buttery smooth.

But in watching the flutter announcement video https://youtu.be/Nu5m1FiS5X4?t=60 (timestamped link) on the screen as menus are opening and the mouse cursor is shown selecting different items, there is... a very perceptible stutter and lag. What is that due to?

Re: Flutter desktop isn’t there yet

#189
post #151

Earlier quoted context omitted.

Well it seems there are 11K open issues and 66K closed issues in their github page. So maybe some issues got fixed at least?

The dreaded, 'closed due to inactivity' strikes again.

Every time I see "closed due to inactivity" implemented, the outcome is that new feature get added rather than fixing existing problems, because the memory of those problems only persists in the users day to day life. The developers have no useful record.

But, I doubt that can scale. I imagine there's some happy place sitting near semi-automated "duplicate" recognition, and a voting system, to give the users a voice. Closing due to inactivity is never a happy place (unless it's sitting waiting for required user feedback maybe).

Post reply on HN