←back to thread

597 points doener | 1 comments | | HN request time: 0.217s | source
Show context
versavolt ◴[] No.46181770[source]
What if you have an excel workbook that relies on a bunch of custom formulas. I would be upset if this happened in my workplace. Datasets have been far easier to handle with lambda, vstack, byrow, and the rest. I would not like this move and would have to remain a holdout. That would also frustrate me because of the division.
replies(5): >>46182126 #>>46182197 #>>46182283 #>>46182638 #>>46183379 #
DanOpcode ◴[] No.46182126[source]
Are we gonna accept being forever locked in to Microsoft because of custom Excel workbook formulas? Forever paying Microsoft a license fee, because we don't want to covert said formulas or invest in open source software to make it reach parity with Excel.
replies(2): >>46182299 #>>46189382 #
1. mmooss ◴[] No.46189382[source]
In many organizations, that license costs less than converting all the Excel workbooks - a process that disrupts work, as only the Excel spreadsheet's creator and user can reliably spec and test the new spreadsheet. And they need to convert with accuracy - worse than crashes is undetected bad output.

Being stuck in legacy systems sucks, and technical people like to deny the reality of it - but it's a business reality.