Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Excel is really good for the wizards and for that one spreadsheet full of macros written by a wizard, which thus can't be ported over to Libreoffice or anything else. Many of those probably should Just™ be made into actual databases, but Excel is a lot more approachable than those, so you end up with giant spreadsheets instead.

For everybody else, Libreoffice is fine as far as functionality is concerned. UI might be another story, but that's worth getting over anyway, especially since a lot of people for whom this is a problem, would also have problems with getting away from Windows as a whole, just from buttons moving and things being different in general.



> Excel is really good for the wizards and for that one spreadsheet full of macros written by a wizard, which thus can't be ported over to Libreoffice or anything else. Many of those probably should Just™ be made into actual databases, but Excel is a lot more approachable than those, so you end up with giant spreadsheets instead.

Yes!! Misusing Excel as a database is really part of the problem. It also causes so many issues. Having multiple data elements within one cell. Someone overtyping a formula in a column of 200.000 values leading to one cell no longer being updated. Needing 32GB of RAM just to edit a spreadsheet with a measly 500.000 rows.

All stuff that never would happen with a real database. Microsoft never really put much effort into making Access approachable.


You could do this in Pandas with Python under like 400mb of ram


Porting involved Excel sheets into web apps has been a decent chunk of my dev career.


What works best in those situations, in your experience?

Do you recreate a spreadsheet, use an existing online service, and/or create a database with proper logic, etc.? If the latter, how do users handle the UI change, and can they have an ease of creation similar to what Excel provides?


In my experience it's mostly about understanding business requirements of people using said excel sheets and then replicating it to CRUD WebApps while keeping capabilities of importing said sheets and exporting them so user flows are unharmed till a wholesale transition is mandated.

Good source of money for contractors as OP said.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: