The browser already renders the page, it's a pretty small step to saving it as an image. After all, there's already a screenshot tool in the developer tools.

Does your screenshot tool let you capture whole webpages, or just what's in the viewport at the current moment?

All these tools are lazy loaded and don't affect browser speed when disabled. The most you're complaining about is the existance of a small bit of extra code in the Firefox download.

What bothers me is that they have engineers working on this extra fluff. Meanwhile UI bugs I reported years ago go unaddressed. It is not a good sign.

This isn't fluff, these are features that a lot of people want.

Link to the UI bug? Sometimes things fall between the cracks.

well, but people usually don't ask for making e.g. the print feature optional because they don't use it and want a lean browser... i mean, you need to draw a line somewhere, sure, but different people will draw it differently.

The 'print' feature is a platform-provided thing. Firefox isn't shipping printer drivers or a printer UI. It simply gives the OS printing subsystem content the user wants to print.

Funnily enough the platform also provides a screenshot system. From another comment it seems like this was driven mostly by user feedback from Windows users, because the ~3 different ways of doing a print screen on Windows are not sufficient and they demand more.

And giving the OS printing subsystem the content the user wants to print requires thousands lines of code in Firefox. Thousands of lines of code many people don't need, while many others do. Just like with any other feature. My parents don't need bookmarks or even tabs, so should we get rid of them in Firefox?

Btw. the screenshot tool of Windows can't capture a webpage properly, only the visible area.

Agreed a line has to be drawn. For me: remove print, remove bookmarks, keep tabs.

That's actually not a bad idea.