I think the problem lies in the fact its not a multi million dollar company writing firmware but outsourced and possibly under staffed and overworked coders in far flung parts of the world.
IMO there are problems in organization of development process. In spite of using outsourcers. First, there is really some centralized
initial repository of codes used in firmware for all routers. It is obvious because this bug with lacking attached device names affects to the wide line of different routers. It is right solution. Re-usability of codes. But what is a real problem, it is in the
lack of synergy among different development teams (or guys). For me it looks like guy (or guys) who is busy with e.g. firmware for R7800 does not know what is going with development for R9000 or XR500, i.e. what guy who is busy with firmware for R9000 is doing. I am sure (practically I know) that they are located in the same office/building or even in the same room. But the same bug already reported and fixed by R9000 maintainer(s) is repeated again in the next release for R7800 by R7800 maintainer(s). I know such real cases. I.e. initial sources are branched like a tree, no unification, no joint common bug fixing, everybody does not know what his neighbor is doing with his branch.
For example, the same OpenSSL versions in the latest stock fw:
1.0.2n for XR500 firmware with asm acceleration (Dec 2017, compiled by Iceway Zhang developer).
1.0.2l for R9000 firmware without any acceleration (May 2017, compiled by Tao Li developer).
1.0.2h for R7800 firmware without acceleration (May 2016, compiled by Haiyan Zhuang developer).
So if e.g. Haiyan Zhuang would re-use OpenSSL branch of Iceway Zhang we could get asm acceleration for R7800 in the stock firmware, not only in my version. If both of them would know what is going in the branch of Tao Li they could avoid the bug with the list of naming attached device. And all of them are not interested in cooperation with me.
And second, not less important.
Management. I dealt with outsourcers and usual developers in the past (my post was chief software development manager). They are interested in new contracted job, sure. Contract, development, they got a money for their release of software. But. There is so-called guarantee period. And all the bugs found during this period have to be fixed by outsourcers for free, no additional payment. So as a rule software developers are not interested in the fast bug corrections (correction of old bugs are payed). It is already problem of management re: how to force them to do fast bug fixing. It is a pity that I am not their software manager ;-)
Well, all this is IMO.
Voxel.