853
German state moving 30,000 PCs to Linux and LibreOffice - The Document Foundation Blog
(blog.documentfoundation.org)
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.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
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.