dash-to-{panel,dock}: better integration or adoption into main code base to prevent breakage on GNOME upgrades
Challenge
As a System Administrator or Consultant, I have been converting Windows & macOS end-users to Linux with "GNOME 3" for years. While I, personally, love and appreciate the current interface of GNOME, it is a real shock to users migrating from legacy or more traditional interfaces. Hence the importance of g-s-extensions, in particular: Dash-To-Panel and Dash-To-Dock. It is also very jarring, for end-users, to have the interface switched back, unexpectedly, to the default GNOME UI after GNOME version upgrades which break these extensions.
Cause
Until the statistician's report that Windows has dropped below 50% market share, due to a surging increase of GNOME/Linux users, I believe that the need for basic UI equivalence options and consistency is very important, especially for on-boarding or migrating new users to GNOME!
I also believe that, like it or not, there will simply be too many users(managers) that will resist/reject migrating to GNOME/Linux without an option to maintain familiar UI work flows from legacy systems. In example: look at how long the MS-DOS interface persisted, despite the Win16/32/64 evolutions!
Solution
Let's prove Linus wrong about ChomeOS being the future of desktop Linux!(https://www.zdnet.com/article/the-linux-desktop-is-in-trouble/)
Please merge, adopt or migrate the basic UI elements from dash-to-panel and dash-to-dock into the mainline GNOME codebase and offer it as a different session, similar to the "GNOME Classic" Xsession, or as an option in the gnome-settings interface, ala "GNOME Panes"(Windows-like) and "GNOME Juice"(macOS-like).
The current dash-to-panel and dash-to-dock extensions can continue or be incorporated into the larger GNOME ecosystem as integrated components that embrace and extend the basic UI elements that become core to the project.