I think you're still not understanding what are we doing and why are we doing it; so, let me explain again:
first, as I mentioned before, this is a very opinionated approach: I don't want neither one single huge JS file including all the code, nor a single CSS one.
why? because, as I've been saying since early 2017, that's a bad idea in HTTP/2 times and is, by no means, a feature that a Python-based CMS must address.
that is, again, my opinion; you can agree with it or not, but I need to make it clear so people understand why we're doing what we're doing.
I don't want to define what tools other people must use and I don't want to fix Plone resource registries anymore. I just want to make my life easier and this approach is a very simple and effective step on that direction.
now, if you understand that, you can freely criticize this approach with more specific claims; I would really appreciate it.
for instance, you can ask why we are registering the viewlet in
plone.htmlhead and not in
plone.footer; that could be a good question to ask as performance reporters like Google PageSpeed Insights and YSlow always complain about this.
well, that was on purpose: people may get rid of Plone footer's on Diazo and disable our features by mistake.
another thing that others (like @thet) have noticed is that we're not including webpack's output in version control, but only on eggs. we're are doing that for the same reason we don't include compiled translations neither.
and this is something that is usual current practice in Plone community now, one that I think must change as we are only polluting the VCS and making life harder to every one.
just check at the number of files added/modified in some recent pull requests that came into my attention:
this is insane and must end for the sake of Belgian beer.