csells

I wouldn't used the hell out of this the last time I was beginning a GitHub action.

I've debugged GitHub actions before and it's a pita. I'd have used the hell out of this!

Dart as a platform provided the unique ability to target both JIT at development-time to enable sub-second hot reload and AOT for release apps, providing native performance when it comes to scrolling, animation, etc.

Dart as a platform provided the unique ability to target both JIT at development-time to enable sub-second hot reload and AOT for release apps, providing native performance when it comes to scrolling, animation, etc.

We find that most developers want their apps to look and feel the same on multiple platforms, with some relatively minor tweaks. Flutter itself handles many platform specifics automatically, e.g. scrolling physics, adding scrollbars, button press effects, etc.

Flutter provides its own widget implementations and does not rely on those provided by the underlying OS. This gives us the ability to give you complete control over scrolling, animation, theming, etc. while still running at native speeds across multiple platforms.

It depends on your definition of optimal. If you optimize for time, then pressing each button one at a time until a Coke comes out. Plus it doesn't take any brain cells so I can get back to coding quicker. : )

Actually, PMs love open, honest feedback. Keep it coming!

Chris Sells PM, Flutter

Flutter 2 contains desktop support at the beta level on both the beta channel and the stable channel behind a config flag.

Wow. You have a great style.

Hey, all. I'm a PM on the Flutter team and happy to be able to fill out the set desktop OSes that Flutter supports with Windows (in addition to macOS and Linux). Got Qs? AMA.

https://flutter.dev/desktop

Dart does have it's own compiler that targets the native instruction set for supported platforms, e.g. 32-bit and 64-bit ARM for Android and iOS, x86 for Windows and macOS, etc. We're experimenting with bitcode in case Apple decides in the future that they're rather have iOS and/or macOS apps be submitted that way instead of ARM or x86, as they already have for tvOS and watchOS.

Chris Sells PM, Flutter developer experience

As one concrete use case, you could use Dart FFI to call Win32 APIs that implement Flutter plugins that support Windows. You should have network access via wifi w/o any trouble today but we do have work to do to support Bluetooth better.

Chris Sells PM, Flutter developer experience

If you're writing Dart targeting Flutter for web (flutter.dev/web) you are able to make calls into JavaScript/TypeScript.

Chris Sells PM, Flutter developer experience

Thanks for the input!

I have heard variations of that most of my life. I always wanted to get into the Unix shell business on the coast so that the following would be true: "Chris Sells sells C-shells by the sea shore." Alas, another dream unrealized...

I'm the PM for the Flutter developer experience. I'm currently digging into the next steps for our desktop experiment with Flutter and I'm very interested to hear how your xplat desktop app dev options fall short. What do you need from an xplay desktop app dev framework and toolchain?

Chris Sells csells@google.com

That's absolutely the goal, Colin. Give it a try and let us know what you think.

Chris Sells Cloud Developer Tooling Product Manager csells@google.com

Mark, if you'd like to try our version of a "web based IDE that gives you access to work with any code you have in your private Google-hosted git repos", check out the Source Editor feature of the Cloud Source Repositories: https://cloud.google.com/tools/cloud-repositories/docs/cloud...

Also, we're alpha testing some integration with the Source Editor and the Cloud Shell right now, so anyone that would like to participate in that alpha test can drop me a line: csells@google.com.

Chris Sells Cloud Developer Tooling Product Manager

Thanks, nt. Cloud-based IDEs are the future, I think. Too many good reasons to have them.

To be clear, this is the current limit in beta and it's per repo, so if you have multiple cloud projects, you get multiple repos. We're thinking about adding support for multiple repos per project in the future. Would that be useful?

Also, and we're planning on upping the limit once we reach GA. What do you think a reasonable limit should be for a git repo? Our goal is to strike the right balance between usefulness and abuse.

Chris Sells PM, Google Cloud Platform

I'm curious what kinds of additional features you'd be interested in here. In these comments so far I've heard code review, access control and online IDE. Would any of those be useful? What else would be useful?

Chris Sells PM, Google Cloud Platform

Of course, we're pretty proud of our git support. We also support "connected repos" where we keep a repo in Cloud Source Repositories in sync with a repo you specify on GitHub or BitBucket; if you make a change on GH or BB, it's reflected into GCSR and vice versa. The idea is that you should be able to integrate with the features we're building on top of GCSR without making you move away from GH or BB. Useful?

Chris Sells PM, Google Cloud Platform