this post was submitted on 21 Oct 2023
398 points (97.8% liked)
Technology
58816 readers
4474 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This isn't a fix. Excel wasn't meant for this. While I do understand it's convenient as a database, unless you're doing something unimportant and small you just really should use something proper. And even now that this "problem" is gone, I am certain there are still more things that cause trouble. You can not satisfy everyone and Excel was just... not made for gene info storage.
Even if you don't want to use stuff that isn't Microsoft Office, that comes with Microsoft Access, which is a proper database management system. It's literally in the same software package, so why do people refuse to use it?
Why would you need a full blown (shitty) relational database management system to store gene info? Excel should be just fine for storing data in arbitrary tables. It shouldn't make assumptions about your data by default, and changing values that look like they're in a specific format should be opt-in, not default behavior.
That is not what it was made for. It was made to do shenanigans with values like doing math on them and plotting graphs. If you merely want data storage, use a table. I agree, a database is overkill for most things, but that doesn't change the fact that Excel is the wrong tool for the job. Maybe if they added a table mode where it's basically just a frontend for a csv it'd work, but right now I'd still say it's better to use a scalpel than a hammer, even if scissors do the trick just fine.
Agree. Excel is terribly inefficient if your goal is just storing data.