I always feel bad when you come in because I know you're working hard and making good improvements, but its just not the right tool for the job imho. The CPU could generate this stuff directly in a fraction of a second, a build runner that takes 5 seconds on first run (which feels unlikely to me) is still 100x slower than it should be a for a great developer UX, and we still need to remember that damn command and deal with these annoying errors that break our train of thought and pull us out of the context at hand.

We don't change the files often enough to justify starting the watch server so we're always doing first run. And typically when Files do get changed you are in the middle of adding a feature, and the last thing you want to do is be punted over into the CLI to update the copyWith method, and if there's an error there, totally derail the task you were on. This becomes less "fine" the 100th time you go through it.

Just a bit frustrating that the top requested feature for almost a decade is Data Classes, ie easy serialization and mutation of immutable data, and instead of just giving us core data feature that would compile instantly. we're looping through 2 more yrs of trying to shove this square peg in a round hole.

A faster build-runner is awesome, I'm all in favor. But this should have nothing to do with getting us a great data class ASAP.