4 ms·
Channeling my inner QA person, this breaks in many subtle and not so subtle ways: - people love to export as CSV. And I kinda understand them, csv looks simple
by makeitdouble 3y ago
Channeling my inner QA person, this breaks in many subtle and not so subtle ways:
- people love to export as CSV. And I kinda understand them, csv looks simple enough, what could go wrong ?
- other spreadsheet softs need to recognize the same field and act the same way. Google Sheets, LibreOffice, KingSoft's one etc. Not counting old office versions that aren't updated anymore, because the owner doesn't want to move into the cloud.
- the flag needs to stay when moving sheets around, copy to another set, etc.
That could still be better than nothing. But could still lead to catastrophic loses as people get used to it working most of the time, there's no perfect solution.
- acdha 3y agoIt might be easier to think about as the difference between perfection and practical improvements. Right now 100% of Excel users are at risk of silent data corruption. The proposed change would allow people to reliably prevent this category of corruption for all of the documents they create and over time that’d become a majority in their field. This would also offer the path for changing the default over time to safe by default. There will be more spreadsheets created in the future than exist now.
- makeitdouble 3y ago> Right now 100% of Excel users are at risk of silent data corruption. They already added an option in the settings last year to deal with this specific issue. Their solution isn't perfect either, they made the tradeoff to optimize for up to date excel users.