freezed VS pack

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.

I've recently found this quote by Kelsey Hightower:

"I'm convinced the majority of people managing infrastructure just want a PaaS. The only requirement: it has to be built by them."

Source: https://twitter.com/kelseyhightower/status/85193508753294540...

In the last few weeks, I've experimented a bit with Flux (https://fluxcd.io/), Tekton (https://tekton.dev/) and Cloud Native Buildpacks (https://buildpacks.io/) on how to provide K8s powered git push deployments without using a dedicated CI/CD server.

My project is still in early alpha stage and just a proof of concept :-) My vision is to expand it into an Open Source PaaS in the future.

Do you think the above quote is true? What does an open source PaaS need to be like in order to be accepted by software developers?

Some other projects have been discontinued in the past (like Flynn or Deis) or were created before the Kubernetes era.

Is it the right direction to provide a Heroku like solution based on K8s or is it better to provide an Open Source Infrastructure as Code library with building blocks to avoid everything from scratch?

```bash (curl -sSL "https://github.com/buildpacks/pack/releases/download/v0.28.0/pack-v0.28.0-linux-arm64.tgz" | sudo tar -C /usr/local/bin/ --no-same-owner -xzv pack)

Although Dockerfiles have the benefit of migrating existing workloads to containers without having to update your toolchain, I definitely prefer the container-first workflow. Cloud Native [Buildpacks](https://buildpacks.io/) are a CNCF incubating project but were proven at Heroku. Buildpacks support common languages, but working on a Go project I've also had a great experience with [ko](https://ko.build/). Free yourself from Dockerfile!

Cloud Native Buildpacks

It's big and overwhelming and sometimes scary. But you know what? It's also fun, engaging, and very refreshing. Because I'm a DevRel, I don't have many chances to focus on something particular. Still, I'm having a lot of fun exploring different CMSs (like Statamic, Craft, or Sanity), new approaches (at last, I understood why the headless approach is so important), and diving into tech I never used before (hello Buildpacks).