Asset Browser is still so WIP because, well, there is a lot of work to do and not much time to do it.
That is something you want for your work, that’s your priority. Blender developers have to take into account many possible ways of using Asset Browser by gathering feedback. So far overwhelmingly people need collection support so work is being done in that direction.
There is no “complete” absence. It’s just scattered across different (open) places.
It was stated before that other data-types is responsibility of modules and community while core Asset Browser team can provide consultation and fundamental code support. As such, there is a patch for GPencil support and work is being done for Geometry Nodes groups.
Brush management is on sculpt roadmap but Joseph have a lot on his plate already to even start discussion regarding that.
@tintwotin has worked on implementing image data-block.
Sybren, developer of Pose Library, no longer working on it, instead he is now developing Flamenco, so further work on animation data-block have to be done by someone else.
Main focus for Asset Browser in 3.0 is to roll out basic Asset Browser as polished as possible. So, you can mark objects, materials and worlds as assets, create thumbnails, have catalog, can drag-and-drop assets. Seems basic to me.
Pose Library seems like different project since it even have it’s own section on pretty release notes.
I’d argue about that. This is functionality that you often use in your work - but that does not mean it’s basic.
That is already the case, you can only enable
Experimental features in alpha builds.
Blender operates on the rolling release basis, it’s not gatekeeping features when they’re ready to be included. You can always improve features later on, including based on feedback that was received upon release.
Alpha/beta build are not for features that are “not ready”. It is for features that will be in release and there needs testing to catch and fix bugs that developers was not able to notice before.
What you want is probably for features to be “production ready”, and there is no rule of thump when that’s the case and we’ll end up with features that could be used by people rot in WIP status. We would not have Geometry Nodes, Asset Browser, Cycles X available for people to this day.
Besides volunteer (and even paid) developers would lose motivation to work on features that will not see light of day until 1-2 years after they’re ready for people to use, even if not perfectly polished.
Or if we would make
Experimental option back in release and put those features in it, things would be the same as before: nothing changes, anyone working with Blender just enables
Experimental option first thing after downloading Blender, making that checkbox useless.