4 ms·
We've been seeing variations of the same article every week. The answer has been the same for a long time: this is great but unfortunately there are advantages
by glimshe 11mo ago
We've been seeing variations of the same article every week. The answer has been the same for a long time: this is great but unfortunately there are advantages in using Office and that's the reason we shouldn't expect mass migration anytime soon.
Excel, in particular, hasn't been unseated despite billions in investments from competitors over the years. Parity will happen someday, but it's at least a decade away.
- hollow-moe 11mo agoArriving first (ye ye Lotus 1-2-3 existed we know) and early extreme lobbyism sure stands strong.
- knallfrosch 11mo agoYou acknowledge your first argument is invalid, handwave that away and then your whole idea of Microsoft's office suite's dominance is "lobbyism"? Good lord.
- nhatcher 11mo ago> We've been seeing variations of the same article every week. Time has come. Over the last few years there is more and more interest from goverments and private organizations to have relieable software that does not depend of foreign entities. Software sovereignty is becoming a necesity rather than a nice to have for both nations and enterprises. > Excel, in particular, hasn't been unseated despite billions in investments from competitors over the years. Excel, like many other technologies in the past can be disrupted. Like mane other commenters say, it won't come cheap. Saving costs shouldn't be the the goal here. > Parity will happen someday, but it's at least a decade away. Challenge accepted!
- glimshe 11mo agoThis is the year of LibreOffice on the government? I'd love if you were right, but I doubt it. The chasm is enormous, and maybe you don't use Excel enough to realize it.
- d3Xt3r 11mo agoThe chasm is enormous, but Calc doesn't need to implement 100% of Excel's functionality when most people - even business/power users - don't use all of its features. What major commonly used features do you reckon Excel has that hasn't been implemented in LO Calc yet, that would be a deal-breaker for most businesses? To my knowledge, Calc has implemented most of Excel's formulae (well over 500 in total count), so at least for typical spreadsheet functionality you wouldn't missing anything. The biggest limitation I can think of is the limited support for VBA, but Microsoft have already announced VBA's deprecation[1], so no one should be relying on it even in MS World. And whilst LO's own Basic scripting is... basic, it also supports rich scripting and full automation via Python and Javascript. It even has a full-fledged SDK for developing addins/extensions using a high-level language like C++/Java etc[2], so businesses who're dependent on some random proprietary excel COM addin or something could invest in development effort to port it over. Heck, if businesses are so inclined, they could modify the LO source itself and build a custom version to add the features they want - that's the beauty of FOSS. [1] https://devblogs.microsoft.com/microsoft365dev/how-to-prepare-vba-projects-for-vbscript-deprecation/ https://devblogs.microsoft.com/microsoft365dev/how-to-prepar... [2] https://api.libreoffice.org/ https://api.libreoffice.org/
- tracker1 11mo agoYou don't use all it's feature, but if you need part of the 10% of features that Calc doesn't support, then your in a world of hurt. When Calc gets the other 90% of the features Excel has, you also need to contend with word, Outlook, Visio and all the rest that Libre Office has a 0% solution for. I support FLOSS... But pretending that anything else does enough for many orgs is delusional. There is work and pain to get through to even have a workable solution... And it won't be as good for a long while. Massive cost savings are one of the bigger motivators... But that will be offset by the need for more internal staff.
- d3Xt3r 11mo agoI don't see why you would automatically be in "a world of hurt". Yes, you might be if you were to suddenly roll it out organisation wide without any testing, but no sane IT department would do that. This is why you have internal test groups and pilot groups. Once you identify the limitations, you scope out the missing features/issues, engage developers if need be, or look for alternate solutions. No one needs to get hurt.