I can't really talk about Ruby. But PHP is much more static and surface of things you have to care about at runtime is like magnitude smaller and there already was opache as a starting point.
And speaking of something like JIT in V8 is of the most sophisticated and complicated ever built. There hasn't been near enough man hours and funding to cpython to make it fair comparison
Even for reducing the context size it's probably worth it. If you have to go back back and forth on both problem and implementation even with these new "large" contexts if find quality degrading pretty fast.
In what way "most powerful"? If you do anything more involved than CRUD it falls apart pretty fast. You can't express most of the things you can do with raw SQL since there is not intermediate DSL like you do with SQLA. You can't hydrate arbitrary object graphs. It's slow, for deep queries building back objects is slower than actual SQL round trip.
It's very easy to use but it's also very limited and i often find myself dropping down to RawSQL or even having SQLA connection in my Django projects.
Faster this, faster that. Is it finally segfault free?
I've tried it like 3 times in span of last year with different projects only to find out it segfaults at runtime or when installing package.
There are many applications where htmlx is objectively the best tool. But i really hate all the hype around it and people pushing it as react replacement.
It's an attempt to solve "player readability". It's common complaint in CS:GO. Many pros play with color vibrance cranked in driver or monitor settings.