I mean, there are some wrong decisions. I would steer you away from Gentoo, because you build all the things, but beyond that, not much.
They present about the same with user space, with some superficial change with defaulting to Unity or Gnome or ... I don't even know the good window managers these days. But you can install the other ones.
And installing is similar too. Either apt install foo or yum install foo, which is not a big enough difference to really get hung up on.
It wasn't always this way. in the 1990s, I went Red Hat (before Fedora existed) because I could not complete a Debian install. I couldn't figure out how to get to "Yes, these are the initial packages, so install now, please". The problem then was that you didn't have yum, so you went to RPMFind to get the packages you wanted.
Then I found Ubuntu, which allowed me to say sudo install this package on the command line and gave me an easy installation, so yay. I stay because 1) I know how to have it tell my code my computer is locked, and 2) because it does The Right Thing with notify_osd. And, of course, because I'm used to it. This means I'm odd, not that it makes sense to you. This is not meant as a recommendation.
I'm hearing Red Hat is common in enterprise situations, including the systems my code runs on that I don't admin, and Fedora is based on that. I know people who run it and, as far as I know, they like it. I see stickers and t-shirts on occasion...
If Bioinformatics is going to be your regular gig, I'd double-up on knowing the Fedora side, even if just it's being used to having /bin/env python pointing to /usr/local/bin/python instead of /usr/bin/python. But it will be much more important to you if you get into systems administration than just developing.
And even then, kinda not, because with Puppet and Chef and Ansible -- are those the only major players in that area? Am I forgetting any? -- you're seeing large systems on which Bioinformatics is done, the admins want to have scripts saying "This machine has sshd, the message queue, NFS mounts to these file systems and that's about it". A Puppet developer told me about a system that caught a rootkit, but every time the kit tried to install the malware server, Puppet said "Nope, not on the manifest" and wiped it. So, installing the packages and keeping it up to, honestly, many generations back for most tools, is a Puppet/Ansible/Chef thing, not a distro thing.
So, if you know people who are strongly Fedora or Ubuntu or Mint and you can ask them questions, go with their preference, but the differences will be small and superficial. It really doesn't matter.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It just doesn't matter.
I mean, there are some wrong decisions. I would steer you away from Gentoo, because you build all the things, but beyond that, not much.
They present about the same with user space, with some superficial change with defaulting to Unity or Gnome or ... I don't even know the good window managers these days. But you can install the other ones.
And installing is similar too. Either
apt install foooryum install foo, which is not a big enough difference to really get hung up on.It wasn't always this way. in the 1990s, I went Red Hat (before Fedora existed) because I could not complete a Debian install. I couldn't figure out how to get to "Yes, these are the initial packages, so install now, please". The problem then was that you didn't have yum, so you went to RPMFind to get the packages you wanted.
Then I found Ubuntu, which allowed me to say
sudo install this packageon the command line and gave me an easy installation, so yay. I stay because 1) I know how to have it tell my code my computer is locked, and 2) because it does The Right Thing with notify_osd. And, of course, because I'm used to it. This means I'm odd, not that it makes sense to you. This is not meant as a recommendation.I'm hearing Red Hat is common in enterprise situations, including the systems my code runs on that I don't admin, and Fedora is based on that. I know people who run it and, as far as I know, they like it. I see stickers and t-shirts on occasion...
If Bioinformatics is going to be your regular gig, I'd double-up on knowing the Fedora side, even if just it's being used to having
/bin/env pythonpointing to/usr/local/bin/pythoninstead of/usr/bin/python. But it will be much more important to you if you get into systems administration than just developing.And even then, kinda not, because with Puppet and Chef and Ansible -- are those the only major players in that area? Am I forgetting any? -- you're seeing large systems on which Bioinformatics is done, the admins want to have scripts saying "This machine has sshd, the message queue, NFS mounts to these file systems and that's about it". A Puppet developer told me about a system that caught a rootkit, but every time the kit tried to install the malware server, Puppet said "Nope, not on the manifest" and wiped it. So, installing the packages and keeping it up to, honestly, many generations back for most tools, is a Puppet/Ansible/Chef thing, not a distro thing.
So, if you know people who are strongly Fedora or Ubuntu or Mint and you can ask them questions, go with their preference, but the differences will be small and superficial. It really doesn't matter.