(I took a cursory look at Chromium [+ NoScript] not too long ago, & did not have enough tabs to go into an "overflow" condition [which Chrome doesn't seem to actually do], but what you describe [& what I now see] is quite a failing, IMO.

You could "finger" wing-it, Ctrl+Tab, Ctrl+Shift+Tab, but that is hardly feasible when you're talking those number of tabs.

I suppose that Chrome users are supposed to be even dumber then FF users.
[At some point, it becomes, how low will you go.])

The number of tabs does not affect performance. In these modern versions of browsers such as Chrome and Firefox, the tabs do not run until you click on them. You can also have hundreds of dormant tabs and do not worry about performance and stability. The only drawback is the inability to see the tabs on the right if it exceeds the limit. This problem is solved in Opera, but it was better solved in Firefox (which had such an option in old versions). They have not done anything like this in Chrome for many years. They did not stupidly someone make so many additions to manage countless numbers of tabs, but I guess someone uses it, but that's not what I mean, just the move buttons themselves.