4 ms·
Yeah, that mirrors my experience pretty neatly. I worked for a small company that at one point wanted to save the licensing costs and had me install OpenOffice
by tpmoney 3y ago
Yeah, that mirrors my experience pretty neatly. I worked for a small company that at one point wanted to save the licensing costs and had me install OpenOffice on every machine for a 6 month trial run. No one issue that anyone had was particularly insurmountable * . But it was death by a thousand paper cuts. Every single person had a different part of their personal workflow disrupted, some requiring work arounds, others requiring learning new tools. But at the end of 6 months it was clear this wasn't going to work, it broke too many things in too many unpredictable ways, and made the little outside world compatibility they did need much more difficult.
* There was one insurmountable problem. At the time OpenOffice still had a 65k row limit that Excel had long since moved past. There was a 5 year old bug ticket opened to fix it, but the developers in that thread were still having debates insisting the users were wrong and that 65k ought to be enough for anyone. You should use a real database if you need more data they insisted. Needless to say, the first time a vendor shipped us a 100k spreadsheet that we couldn't open, the writing was on the wall even if no one else had had other issues.
- MadnessASAP 3y agoJust this morning I made a mental note of Power BIs 1 million row limit in certain circumstances. I don't have any immediate plans to pull a million rows right now but I could see it happening. 65k would be easy to pull off, a year of some poorly formatted data blew through that recently. (I did push 10 million rows but that was by accident, some Power Query code got a little greedy)