Flutter VS freezed

[3]: https://github.com/flutter/flutter/tree/master/packages/flut...

Thanks - that link does not appear to be open access, anyways I don't think I've seen it. I'm familiar with Flutter at a high-level (Kevin Moore gave a great talk on it at Wasm I/O), and I think other than requiring users to work in Dart, it is probably one of the most powerful ways to do cross-platform UI today.

Worth noting that their original GPU backend was Skia, and now they are retooling around Flutter GPU (Impeller)[0], which is kind of designed similarly as an abstract rendering interface over platform-specific GPU APIs.

[0]https://github.com/flutter/flutter/wiki/Flutter-GPU

If you are considering Electron/React then I would suggest adding Flutter to your list of technologies to consider. It uses Dart (a language similar to C#) and has a lot going for it… relatively quick to get up to speed with, fantastic developer experience (e.g., hot reload, great IDE support, good development tools) and very strong cross-platform support: it generates native iOS, Android, MacOS, Windows and Linux executables. Check it out: https://flutter.dev/

You can find the React Native documentation here and Flutter Documentation here.

[1]https://github.com/flutter/flutter/issues/55092#issuecomment...

> There is actually a great issue thread on the Flutter GitHub that explains exactly why other solutions do not work correctly when compared to hooks [0]

Interesting. I assume you are referring to this comment in particular -> https://github.com/flutter/flutter/issues/51752#issuecomment... ?

There is the `sealed` class modifier which allows for exhaustive matching on possible types: https://dart.dev/language/class-modifiers#sealed

There's also a package called freezed which offers similar utility (you might already be familiar with this seeing as you mentioned pattern matching): https://pub.dev/packages/freezed

I recall there being a reason unions aren't generally implemented, though I'm not sure where I read it. It was to do with union types being unnecessarily complex for the compiler and the code they tend to produce, at no real benefit to the programmer or the resulting program. Go's lack of unions is essentially based around the same reasoning.

Interesting. May I ask how this differs from something like Freezed https://pub.dev/packages/freezed and its from/ToJson features ? I haven't used it yet, but I'm just curious about the concept and use of these sort of packages.

The official site does show what you can use it for but to explain a bit more, it helps you work faster.

One rather minor suggestion: it took me a while to understand exactly what the benefits were, but the example shown on this page of the docs summarized it well. I would suggest showing an example like that at the top of the main Readme and first page of the site, before or right after the motivation section, similar to how Freezed immediately shows its value proposition.

Read more on what you can do with Freezed.

freezed on pub.dev

We use freezed for our models, and then use withConverter in the firestore SDK to easily translate between firestore and our models... however we run into issues with concurrent updates to documents.

Once the package has been created, we will install freezed for JSON serialization and value equality , as this library provides helpful tools for these tasks. We will use json_serializable for JSON serialization. To install freezed and freezed_annotation, open your terminal inside the models package and use the command:

Data class: freezed

I've recently been exploring a codebase which is heavily using Freezed with Bloc. The resulting code base is almost an entirely different language altogether, and comes with almost triple the files of a non-freezed codebase.