Idea: when Dark's Dark code can be in a package, it should be

[StachuDotNet]

#4384 (comment)

I've been imagining that, long-term,:

• what can be written in Dark (rather than dark repo), should be written in Dark
• out of the stuff that can be written in Dark: if it can be written in a Package, it should
• one's editing experience comes with several 'default' packages (maybe this is per-canvas?)

Does that make sense to you?
I think this is a nice way to provide a composable experience, and will push us to have a good package infrastructure and ecosystem.

[pbiggar]

I agree with the first two, with emphasis on "long-term".

one's editing experience comes with several 'default' packages (maybe this is per-canvas?)

This feels very specific, I'm not sure what this really implies.

[StachuDotNet]

for example:

• a 'common refactorings' package exists
• when you create a new Dark canvas, that package is 'present', such that you can immediately use the functionality availed by the package