https://bugs.documentfoundation.org/show_bug.cgi?id=37134
--- Comment #130 from Roland Hughes <[email protected]> --- (In reply to Roland Hughes from comment #129) > (In reply to sumbuddy99 from comment #128) > > (In reply to Roland Hughes from comment #127) > > > > > > > > You can't just "add tabs" to a monolithic pile of legacy code. Too many > > > developers over too many years. > > > > > Not only can you, it's already been done. Many, many years ago, IBM took > > Open Office, added their own (IMO better) interface, with tabs, and called > > it Lotus Symphony. When they discontinued Symphony, they donated the code to > > the community. It may take some tweaking, but it does not need to be created > > from scratch. > > I have pointed that out many many times. Posted screen shots of it and > written blog posts about it. > https://www.logikalsolutions.com/wordpress/information-technology/lotus- > symphony/ > > The powers that be deny deny deny they ever got that code, but somehow they > got the Navigator. It was this book. https://www.theminimumyouneedtoknow.com/agile_book.html This problem has been there for a ___very___ long time. https://www.logikalsolutions.com/wordpress/information-technology/speeding-up-libre-office-6/ https://interestingauthors.com/blog/technology/libreoffice/ https://interestingauthors.com/blog/technology/why-people-pay-400-for-wordperfect-professional/ Every machine I install any Linux distro on I immediately un-install Libre Office and install TextMaker, sometimes just OnlyOffice desktop. I haven't looked at the code for LO. I can tell you this has all of the signs of something that got decisions made allowing it to run on Raspberry Pi and other RAM restricted environments. This means you continually make tiny allocations instead of looking at how much RAM is "free" and allocating the smaller of half or 1GB and repeating that allocation every time you need more. OOP allows slopy developers to write a great many things. Problem is they don't run well. Yes, I've been a developer for many decades and worked on many different platforms including embedded systems for medical devices. The problem with allocating objects one at a time is you end up with a lot of memory fragments. Dynamic memory allocation for most compilers on most operating systems is pretty bad. For small things like a 100 page document that is text only or has very few images, you don't notice it. To really test something like that need a document containing at least 450 pages and over 30 re-sized images with text wrapped around them. Most importantly you need to run it on a 4th gen i7 or lower class machine with a spinning disk. Honestly, performance testing should probably be done on a 3d gen i5 having a spinning disk. I wish you well, but I don't use LO anymore, not on any computer and I have quite a few of them. Just can't justify the lost time and pain. A project this old isn't going to make architectural improvements. It would require a re-design followed by a re-write and require 2 highly skilled people in a room together for a year or more. Not going to happen. This will take the Microsoft path of "Just throw hardware at it." -- You are receiving this mail because: You are the assignee for the bug.
