The Post Ninja

  • 0 Posts
  • 11 Comments
Joined 3 years ago
cake
Cake day: July 8th, 2023

help-circle


  • Blaster M@lemmy.worldtolinuxmemes@lemmy.world•Of course
    link
    fedilink
    English
    arrow-up
    25
    arrow-down
    2
    ·
    12 days ago

    This. As much as I want LibreOffice to succeed (AND I WANT LIBREOFFICE TO SUCCEED SO SIT DOWN YOU IN THE BACK), having converted actual work projects over to LibO and maintain them has been hell, to say the least.

    2026 and tables and text boxes still explode the document into confetti if you look at it funny. Hours of frustratingly reconstructing documents, or reloading progress saves because moving a text box one pixel over makes things explode.

    LibO needs QA and maintenance fixes, badly. If you don’t want LibO to use AI models to bug hunt, then enlist and help fix it. Development in turning LibO from a messy desk project to something actually useable efficiently has taken literal decades already.





  • Unified memory hasn’t been the norm for a long time. The stranglehold is the bus connecting the memory to the graphics. SoC designs can bypass the strangle since they put the memory and gpu on the same die or literally next to it.

    Having unified memory means removing unnecessary copying of data between memory segments, saving both memory usage, cpu and I/O time, and energy, especially as integrated systems (SoC) use the same literal memory chips for both things.

    Basically, memory should not need to be dedicated to any task at all, it should be available to be allocated and referenced as required by the task that needs it, but since historically gpu memory and system memory are different memorys that require data to be loaded in either or the other, we are stuck with that paradigm in apps writen with that divide in mind.