If there are asset manager addons, it is because python API allows them to exist.
There is no reason to be defeatist and consider that final asset browser will be terrible.
Current asset browser is not broken. It is half build. That is an important difference.
Blender developers are not incompetent. Their work in progress is open.
And real problem is that users/developers communication is always confusing about status of features.
To caricature :
- Developers always consider that current state is just a milestone before next one.
So, it does not matter if lack of abilities is not allowing to complete workflow.
- And users are always expecting that : at the moment, the idea is evoked, developers will deliver a perfectly working feature in the following hour.
It will be great if everybody was respecting the work of each other.
Currently Blender2.8x, 2.9x, 3.0 are frustrating users because those are releases corresponding to transition with 2.7x or accumulation of first milestones about a design that is supposed to become fluent when second milestones will be settled. And a lot of those lacks are currently filled by addons.
It is expected for a Free Open Source Software that people will contribute to its code.
That is something that is not happening at the scale people of Blender Foundation expected, for various reasons.
The ability of Blender Community to accomplish 2.8 design in a reasonable amount of time has been overestimated.
And now, that work corresponding to first milestones has been done, everywhere ; there is no U-turn possible. We are forced to wait for developers to reach second milestones.
Most of those milestones has been listed into d.b.o tasks. We should not be talking about those ones.
We should be talking about things that are not on developers list. IMO, UI discussion has been interrupted too soon for many stuff to allow developers to pass to another subject and pretend that Blender 2.8 or 2.9 was there.
Probably for same reason, we will have a Blender 3.0 release that will continue to suck in many areas.
When an UI refactor is announced, there are lots of people coming from other software starting to interfere. Yes, their remarks are pertinent about discoverability, readability, etc… Are they in phase with community abilities, management, history ? No.
To me, there are basis of UI that are not robust.
Inability to place Adjust Last Operation panel at a fixed site, anywhere in UI.
Inability to manage several columns of panels in Properties Editor.
Inability to customize Toolbar with desired active tools and addons buttons.
Inability to customize menus without scripting.
By default, we have lots of operators that are working on all visible objects or just on active object. But we are often missing equivalent to work on a selection or a collection. Instead, we are losing time in copying/pasting.
To me, that is a lot of work that will not be solved by few weeks that will be dedicated to UI workshop.