nats-dart VS plugins

NATS has it's own custom text based protocol, and the client ecosystem is not as mature as others', like MQTT. In fact, I developed the NATS Dart client initially to be used from Flutter apps, but now can be used on Dart servers as well. Ivan from NATS is currently working on native MQTT v3.5 support (releasing sometime soon) and v5 support landing in Q1 2021 (Source: NATS Roadmap). I see here that they're building the Go implementation from scratch, which is interesting. They also seem to be converting every MQTT topic to a NATS topic for backward compatibility (obviously, duh) - I'm not sure if this brings any challenges down the line.

(This new version will be endorsed by google_sign_in: ^6.0.0, once this PR lands: https://github.com/flutter/plugins/pull/7191, probably next week. This was made a major version change so people can test and update at their own pace.)

Looking at the web version of the video player package which doesn't use textures but VideoElement DOM nodes, I'd guess that textures aren't supported.

It's not 100% true that Flutter doesn't offer any first party native features. These plugins are maintained by the Flutter team: https://github.com/flutter/plugins/tree/main/packages

Here's an example: https://github.com/flutter/plugins. As you can see, that repo has no "issues" tab. And it mentions that issues should be created on the Flutter repo itself

There's work in progress to create a new camera plugin using CameraX: https://github.com/flutter/plugins/pull/6158

Find the example wiring in the Google sign-in example application.

image_picker

shared_preferences

The plugins is missing Issues tab currently. It's hard for developers who need to raise or find issues on packages.