That's really neat, so you don't have to configure your system to download all the packages i mentioned?
I assume you'd have to configure it. I don't think it just magically works.
You do have to do some setup, but it's often as simple as
brl fetch <distros>
to get it to support the given distros' package management system. For example, if you want access to Debian's, Fedora's, and Arch's packages, you could run
brl fetch debian fedora arch
and wait a few minutes for it to fetch and setup the corresponding subsystems. After that, you can run apt, dnf, and pacman pretty closely to exactly how you would on the corresponding distros.
It's probably not right for me since this is geared towards pretty advanced linux users (who've used more than mint, Ubuntu, raw debian, mx, Ubuntu Studio, and Fedora...)
Bedrock doesn't necessarily require someone to have experience with different distros, but rather just the distros they're interested in getting features from. If you as a potential Bedrock user just want a system that mixes features from Ubuntu, Debian, and Fedora, you've done all the distro hopping Bedrock would ask of you.
That having been said, Bedrock is
arguably better suited for generally more experienced Linux users, just in terms of depth rather than breadth. Bedrock systems are, by their very nature, more complex than traditional distros. If you're not already fairly comfortable with the distros you're getting features from, this lack of comfort will compound as you mix in more distros. If you're just using one distro, you just have to understand that one distro to avoid headaches.
without getting too off topic...the internet and poverty don't go very well together seemingly. I live in a pretty rural and poor place in the US, it took me years to figure out which would be the best ISP for me since the ISPs don't tell you!
While what prompted this was Arch rather than Bedrock, it may be worth noting that Bedrock exacerbates this concern. Bedrock systems often have redundant instances of common dependencies (e.g. multiple otherwise incompatible libc instances), and so regular updates end up updating more things than on traditional distros that can more tightly deduplicate dependencies. This results in more bandwidth consumption than on a traditional distro.
Arch seems great but i've gotten so used to my set of programs and habits, that switching over is kinda frustrating. You have to learn all these new commands to even get it installed, which i would have been more open to when i was getting out of windows.
Bedrock actually helps with this via its package manager manager ("pmm") utility. The main purpose is to let you do multi/cross package manager operations (e.g. update all the packages, search all the package managers and install the highest configured priority one that offers a given package, etc). However, it needs some command format of its own, and in keeping with Bedrock's spirit of letting you get features from other distros, it lets you configure pmm to act like other package manager interfaces. As a result, it effectively lets you translate package manager interface formats across package managers. A Bedrock user doesn't necessarily have to learn all the package manager user interfaces.
That having been said, the user does need to know other parts of the corresponding distro, such as how to configure the given package manager; if the learning curve for a given distro as a whole is problematic, pmm's assistance with the package manager command line interface is of limited value in resolving this concern