Was die Frage im Jahr 2010, ob das MS Office für Studenten einen Fehler hatte?
Was die Frage im Jahr 2010, ob das MS Office für Studenten einen Fehler hatte?
Ah, I wasn't aware OOo was no longer being developed. In fact, it seemed like LO wasn't either, so I checked AOO first. If you look up the details, you'll notice they still mention Apache OpenOffice and are still in development as an alternative to OOo, so I tried installing it. But AOO didn't work properly on my W11. I installed it on my W10 laptop without issues, but when I switched to my W11, it stopped working due to compatibility problems. I also tried Libre Office, MS Excel, Google Sheets and a few others, but something damaged my original file, making it hard to fix. I managed to partially restore it by uploading it to Zoho, and then another repair involved copying and pasting after moving it to Excel from Zoho. Eventually, the cut-and-paste issues returned, so I moved it to Google Sheets where it has been functioning well now.
Honestly, AOO, LO, Google Sheets and similar tools each have their own strengths, but none quite match Excel in performance.
I hope this clarifies your question. Thanks for the suggestion!
I prefer Libre Office since it's open source and free, and it's actively being developed. I came across a YouTube video explaining how Apache updated AOO, but upon closer look, it seemed the updates were just small semantic tweaks with no real development happening. I don't have a link at the moment, but I think I can find one by searching.
I handle my own backup in a slightly unique way. At home, I run Linux as my operating system while exploring its features. I noticed it offers some advantages over Windows. I don’t keep files online due to trust concerns, but I rely on a USB stick for regular backups. My method uses a command-line tool named rsync, which works alongside the standard shell (commonly called a command line environment) to perform backups with versioning. This ensures each file in the target directory gets a backup copy, preserving history and preventing loss if something goes wrong. The command I employ resembles this format: