https://bugs.documentfoundation.org/show_bug.cgi?id=167313
--- Comment #3 from Telesto <[email protected]> --- (In reply to b. from comment #2) > Yes, it's not useless, however a better coding discipline and some rework > might be beneficial. Not sure if it's coding discipline. Say: table layout isn't static, it's calculated on the fly on each edit. And there plethora of variables. Embedded tables, with embedded tables again. Merged rows, merged columns. Different font sizes. So bugs are supposed to happen. It's highly complex. Each time the 'refactor' certain area to accommodate today's need, new bugs get introduced. From stuff that got overlooked too, old code simple working by coincidence, to performance issues with compatibility layers, bugs being masked by certain behaviour Their is plethora of reasons A) primary lack of resources: developers (enough bugs in the bug tracker) So some developer will take up the task to refactor area XYZ. However gets 'flooded' by the fall-out. Unable to address it all alone (feeling overwhelmed). Others are simply starts collecting the bugs, so he/she someday able to fix those bugs at once when 'familiar' again with the code and when he she has time. B) Lack of testers C) fixed release schedule. Each time presenting something 'new'. With changes made last minute; with no time to check for side-effects. Holding off has no purpose either: as stated above: lack of testers. Nor developers to solve them. D) Need to compete with competitors. Adding half-baked features to be able to compete. However issues aren't ironed out by lack of resources to fix them (and/or testers to find theme before release) At the developer side A) Volunteering developers have only so many free hours and needs to be 'fun'. Aside from personal life changes. Getting married, having kids etc. The move on B) Paid developers are able to spend more hours. However the must be feel up to the task; the also need enjoy working on the code. Coding can be terrible frustrating; whack a mole Ideally there is an 'army' of lets say 30/40 full time paid developers working 5 day's a week improving the code (based on the size of the project). With a support team in the background. In reality it's more of 5-10 (part-time) developers, most hired by an eco-system partner getting X time from the employer to work on LibreOffice at choice or getting a designed task (or something like that). So couple of weeks nothing, couple of changes, and back to radio silence (busy with other tasks). The whole project is quite understaffed and/or overambitious, IMHO. The result is pretty decent seen from resource perspective. However not the quality product, you might expect. And the general quality isn't improving incrementally over time either: One bug being replaced by another on in the same of different area. Sometimes I get the feeling (subjective) it's getting worse: more large refactors where done, without addressing the loose ends. Ok, by some measure it might be improved: number of crashes likely less compared 5 years ago; in my perception at least. -- You are receiving this mail because: You are the assignee for the bug.
