I'm not doing a poll. I think the real concern is that we can't assess the return on investment (ROI) of a given change. Sure, we can rank order our preferences, but how valuable is this if it turns out that our #1 item would take 4 weeks and we could have #2 through #10 in the same amount of time? I know I'd change my vote if that were the case.
Thus, to some extent, our voting does a disservice to the dev team. We sort of need to trust them to do their job and prioritize based on their impressions of ROI. Fortunately, they are very engaged with the community, so it's not a bad spot to be in.
Organizing based on categories would just be a nice QoL improvement for the QoL list. It's gotten so large that it's hard to parse. My concern is that if a dev were to look at this now, it's probably so intimidating that it's easier to just ignore it altogether and go do something else. My hope was that this would be stuff they could tackle one or two at a time when they have spare time between larger tasks, need to get back into the groove, etc., and I fear it no longer serves this purpose.