Again - its an attitude thing.
Retroarch so far has gifted us with an implementation that.
- Isn't compatible with the Switch standby/resume screen in a reasonable/normal way.
- Disables the screenshot button on the system for no reason, other than the libraries they went with not supporting it
- Showed no interest in any of the Switch specific modalities, be it the one>two controllers thing, rotatable screen with controllers detatched thing, prepopulated config files, that would actually point to the folder path conventions
- got none of the menu stuff working...
And tells us, none of that is a priority, or should reasonably be expected anytime soon. Currently they are championed for getting rid of a crash that would happen on every exit - and people are screaming, that they can smell a release candidate.
Instead we get *BS* attitute fronts for critizising, that retroarch sill follows the same bloated, seven year old design principle, that doesnt even know savestate images, or core settings that are front and center.
If you ordered the Cheerleader squad, you still have the one youtuber in here thats always very excited, to make a video whenever a new build gets shared, but honestly - this is starting to look like a lackluster experience from beginning to end. And when we address it, we dont expect to be matched against "attitude plays" or simply being ignored, for having brought it up.
Retroarchs devs didn't care jack to look at other contenders in this space (cpasjustes pFBA buil), they are better in every way. The only reason I'm still using retroarch is because there are no alternatives. I very much would like to use an emulation option, that follows more current design principle.
Also expect them to be called out for there utter ignorance in respect to Switch specific features so far. It really takes a lobotomy to accept the "screenshots button not working is not a big deal", because Albums is remaped to HBL, anyways - as any sort of explanation.
You do realize the Switch port of Retroarch has
no devs assigned, right?
There is no assigned person or dev to work on the Switch stuff yet.
Heck I don't even know if one of the devs has a 3.0.0 Switch yet, as far as I know none of them do.
So far all the fixes that have been made are from libtransistor commits, not RetroArch's.
The last time the Retroarch repo got a specific Switch commit was like 2-3 days ago by misson, one of the libtransistor developers, and as you can guess, their priority is not getting Retroarch to work, but libtransistor instead.
They are backporting and/or implementing stuff from scratch, like SD access and JIT support (which roblabla said he will work on after SD).
Oh and also both
@roblabla and @misson20000 (the main contributors to libtransistor on Github) barely get online here, so really most of the stuff that we are seeing lately is by either them fixing/adding something to libtransistor, to a user who has a proper compiling environment for Switch's NROs.
Most of the glitches/crashes right now are due to libtransistor still going through changes, and roblabla has been kind enough to listen to the feedback and try to fix them. And as we can see things are getting slightly better.
Now, as I have specified in the OP, RetroArch hasn't been ported using libnx instead, and no one has jumped into it yet.
Comparing RetroArch to pFBA is not at all a fair comparison, because to begin with pFBA has a proper assigned dev focusing specifically on the system, and using libnx from the get go, which is an entirely different beast. Add to that the fact that he is using only pFBA's source code, and not trying to handle multiple cores/emulators at once like RetroArch does.
To end all of this, take into consideration as well that from the whole people posting here, NONE of us are developers, only the two I have mentioned, and they don't go online here often, so you can see that your posts are not being ignored, but the issues that have been posted are unknown at the moment because most people are simply users and cannot replicate the issue some are experiencing, and without reproducing it there is no way to help out.
To be honest, RetroArch is the best option we have to be able to run multiple emulators on the Switch.
If you don't really like RetroArch's "old design principle", then I have nothing more to tell you other than:
Good luck waiting for someone to make specific ports out of each emulator.