860
German state moving 30,000 PCs to Linux and LibreOffice - The Document Foundation Blog
(blog.documentfoundation.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Apr 2024
860 points (99.4% liked)
Linux
48721 readers
965 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
If an Excel sheet is that big, it should be replaced with a proper database, which most likely would run on Linux. I think you're right, though, about the lack of planning around the practicalities.
Using the right tool in an office setting isn't something that's typically done. Unless that tool is a spreadsheet of course. A spreadsheet is always the right tool.
There often aren't spare funds to develop something proper.
What is the best sheet to Db Tool out there? Surely this is a normalized path by now, right?
you can probably just use python (pandas or something) or an equivalent in other languages
In structural engineering (bridge design etc), we use quite complicated spreadsheets for calculations; a database wouldn't be the right tool for that job. We use excel because everyone knows how to use it and it's easy to print to PDF and see the inputs and outputs and any graphical summaries you have added. Using a spreadsheet makes it easy to check and easy to adapt/change when you want to do a slightly different calculation next time.
I've tried building spreadsheets of similar complexity in libreoffice and it's true they are very slow in comparison and more prone to crashing.
Libreoffice works well for some tasks and I enjoy using it at home but honestly if I tried to use it at work it would cut my productivity significantly. I'm probably using it more intensively than most people though.
I agree that spreadsheet use in engineering is one of the most complicated use cases, but I submit for your consideration another very complicated use case: laboratory software ( https://en.m.wikipedia.org/wiki/Laboratory_information_management_system ) LIMS do what Excel can but with the added benefits of being more controlled, secure, user friendly and faster because they're built upon the back of a modern database. In my experience with engineer built worksheets, the engineer that built them is typically the only one who knows how to use them. This is job security for that engineer, but isn't scaleable for others' use. In the lab software, a scientist builds the methods, and lab technicians use those methods over and over again daily. Each step of each use of the method is recorded with the inputs, the results, who performed it and exactly when. The workflows are built-in and the calculations are comparable to those used in engineering.
Interesting, I think it's different for structural engineering because you're doing calculations in accordance with a code of practice and the spreadsheet needs to be adapted to tweak the inputs and outputs of a standard formula and apply it slightly differently for different bridges / structural arrangements. I've written loads of spreadsheets that have been used and adapted by other people in my company, I honestly don't think they are that difficult to understand (or people wouldn't have been able to build on them and adapt them).
I can see that lab software is quite different, especially if you have very well defined procedures and you are repeating exactly the same test again and again with the same inputs and outputs.
Ah, yes. Easily adoptable by coworkers + low repeatability = no need to change. Stick with spreadsheets.