<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - LibreOffice font blurry on MacBook Pro's Internal HiDPI Retina Display running macOS Big Sur 11.0.1" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138122#c44">Comment # 44</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - LibreOffice font blurry on MacBook Pro's Internal HiDPI Retina Display running macOS Big Sur 11.0.1" href="https://bugs.documentfoundation.org/show_bug.cgi?id=138122">bug 138122</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to Samuel Mehrbrodt (CIB) from <a href="show_bug.cgi?id=138122#c43">comment #43</a>) > (In reply to Telesto from <a href="show_bug.cgi?id=138122#c41">comment #41</a>) > > Solving this particular problem maybe not the best investment. Even if this > > would solve the issue here. > > Please don't keep contributors from working on what they think is worth it. > Thanks! Everybody should work on thing they see think is worth it. Totally true. Not intending to discourage/scare off people to do what they think being they right thing to do. However I found it necessary to put the case in slightly broader perspective/context. A kind of 'inform'. At least that was my intension. I admit having some political reasons. They pressure to implement Skia with HiDPI functioning within tolerance, font being OK, and image in table not lagging simply less. So they short term fix here will of course delay further improvement, until the next big issues appears. While lots smaller flaws - nobody gonna fix for macOS specifically - kept, in my perception, unnecessary around. [They would simply disappear with Skia, based on my limited knowledge on they topic]. And for they next big issue related to rendering they whole process starts again. Solving they issue at hand or patch they specific problem. The whole cycle can go on for a while. And every fix-up will being costly business too :-(. Looks cheaper for the 'actual fix'. But pricey solution in the long run as they big overhaul must happen anyhow someday some time (How much time did Stephan/Tor spend on they now broken hack). And they developer budget and the number of available developers for macOS being nearly 0. macOS edition simply lifting with they Linux version. Most of they macOS backend is old barely maintained OoO . As long as it works within tolerance margins, it works. Ain't broke don't fix :-). So in long term sense perceive Skia better solution. It's simply a conflicting message for the short term. Caught between a rock and a hard place. In they worst case this bug kept open for months/years, because they needed 'pressure' build-up not being enough even with this bug open. Surely not the first time people had to wait. They love for macOS isn't that big. It's really a niche product. They whole thing is still running thanks to Tor spending time on it. In part in the role of being employee and a part in his free time (if i'm up to speed) In my perception Skia will remove some of the maintainment burden. However it's an investment up front. Anyhow, my 2 cents. Fixing they bug here will make quite bunch of people happy :-). In a few weeks they CC will explode to 50 people or so.. All having a actual/current problem. And care obviously - and surely not without reason - less about they long term strategy, but want a fix for current problem asap. And speaking about strategy kind of tricky in a world where this doesn't exist, as - TDF - being a project. However not necessarily most efficient, but they same hold true for strategic thinking. COVID ruined lots of long term strategic (business) visions (number of new cars sold) and while speeding up changes in other area's (say working from home)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>