Whilst I agree that there is a good argument for a for a simple implementation, cakeQoS-Merlin and FlexQoS do different things:
- Cake (using besteffort) is currently providing excellent (almost magic ) queue management with all traffic having equal priority
- FlexQoS is adding better traffic shaping / prioritisation to the built-in (to Asuswrt-Merlin) algorithms
Cake already supports multiple configuration options including diffserv3, diffserv4 & diffserv8 which are designed to support shaping / traffic priority based on DSCP marking directing traffic to different tins, but very little of my traffic seems to be DSCP marked and therefore most traffic is processed in the besteffort tin. This means that when demand for my bandwidth is seriously over subscribed, I still suffer problems with large downloads getting a fair share of the bandwidth when competing realtime traffic such as voice calls and video streaming don't have enough to run successfully.
What would be amazing would be to have cakeQoS-Merlin offer a simple install and forget implementation for those that don't need any more, but for people who want to have shaping available too, make advanced options available which allow multiple tins to be implemented and use the built-in Asus / Trend traffic identification functionality (and maybe with some of the extras offered by FlexQoS) apply the DSCP marking to traffic.
I think there is still much work to do on the initial implementation, but I would love to see this continue towards looking at something similar when time permits.