Welcome to the community.
This topic comes up often, and part of the confusion comes from how Bambu Studio has evolved. It isn’t built from scratch. It inherits large portions of its functionality and structure from PrusaSlicer and OrcaSlicer, which themselves trace back to Slic3r. That lineage isn’t a problem by itself, but it does help explain why the UI sometimes feels inconsistent.
A clear example is the pair of competing File and Edit menus. They perform overlapping roles, but they’re organized differently and don’t follow a single design convention. Instead of guiding the user, the layout creates hesitation because the same category of actions which the Windows Style and what users are used to, appears in two places rather than the nested approach all other desktop apps typically follow.
To put that in context, Microsoft had at one time published a style guide and since 1989, that standardized the classic File, Edit, and Format structure. Most users expect that pattern because it has been consistent across decades of software.
The open-source ecosystem, however, often drifts from established patterns. That isn’t because developers are careless, but because many tools evolve organically over long periods, with multiple contributors adding features in isolation. The result can be a UI where new functions get bolted onto whatever space is available instead of following one unified design philosophy.
In slicers, this shows up as overlapping menus, inconsistent terminology, and workflows that shift depending on which part of the interface you’re in. None of this makes the software unusable, but it does make it feel less coherent than it could be if it followed a single, intentional design standard.
But hell… if we don’t like it… well… we can always demand our money back from the developers. 
The folks at Orca should be given a respectful nod here. They are fellow 3D printer enthusiasts who enhance the Bambu Source code with the goal of improving the quality of life features in the UI and they do this for the love of the technology, not for pay. They also bring back much of the functionality that was not brought over from Prusa and Cura slicer which Bambu heavily borrowed from. Sadly, Bambu’s recent community-hostile behavior has left an embargo on future compatibility with any of their new products so unless you have a pre 1.04 firmware X1 or P1, you’re not going to be able to use Orca Slicer which many feel is superior in many ways. Oddly enough, Bambu Competitors, Anycubic and Creality have both embraced Orca Slicer as their underlying engine giving a nod to the Orca devs for doing a great job.
Bottom line: don’t expect Bambu to make quality-of-life changes to Bambu Studio unless they decide to pull the idea back from Orca, which they often do. If you want a feature, frame it in Bambu-think: how it increases filament sales or how it helps sell more printers.
. Here are the issues that have bothered me over the past six months:
