Thanks, these are useful gaps to call out.
I’ve split this into two feature requests:
For printing, I think this needs to be designed as a proper desktop printing pipeline rather than only adding System.Print(...) methods. A good API probably needs printer/page setup, printer discovery, a print job lifecycle, page rendering, and a Graphics surface so the same drawing model can later support PDF export too. Convenience methods for printing text or pictures can sit on top of that once the underlying model exists.
For the about box, I agree there should be a built-in way to show one using the app’s project metadata. I’m not yet sure System.ShowAbout() is the right final location; it may belong on Application / DesktopApplication or another desktop-specific API so it does not mix desktop UI behaviour into the core runtime System module.
Both are now in triage rather than scheduled, but they’re tracked.