It might not be friendly for new Linux users but I feel in control using it and keep it maintained and clean easily.
I usually recommend Vanilla OS for non-tech savvy people, in case you're looking for something that just works. It will probably become limiting for you after a while since you like tinkering.
For users switching from Arc, there is no good alternative, but Firefox with Sidebery and custom CSS comes close.
In other words, the ability to see two browser sessions, side-by-side, with a vertical split between them. Two viewports, each with their group of tabs. The same type of view you can get in, for example, Notepad++ with its "Tab>Move to Other View", or Visual Studio's "Tab>New Vertical Document Group".
I frequently arrive at situations where I want to compare the contents of one webpage against the contents of another webpage. So far, the most usable option I've found is to split the 2nd tab off into a new window, then arrange the two windows side-by-side.
There is "Side View"[1], but that shows a bare viewport, which makes browsing in the 2nd viewport much more restricted than regular browsing.
[1] https://blog.mozilla.org/en/products/firefox/its-a-new-firef...
You can take my list comprehensions from my cold, dead hands.
There isn't a use case I've seen where these types of mini languages fit well. Ostensibly, you could give it to a user to write to query JSON in a domain-agnostic way in an app but I think it would just confuse most users as well as not being powerful enough for half of their use cases.
Sometimes it's better just to write code.
What if the query is implemented in a lower level and more efficient programming language, or probably a completely separate DB engine.
It is unclear why that having multiple different browser engines is strategically important. As far as I know we've long left behind the world where a hobbyist project could reasonably expect to implement modern JavaScript. Brave's existence and success suggests that competitors building on Chromium are viable.
Not to say it is a bad thing to have alternatives floating around; but at this point it is probably easier to have multiple forks of Chromium than strive to have code with a completely independent genealogy.