You'll have none of those in 8.3, guaranteed. Offering alternatives to Jython is something we want to do, but as I mentioned in the dev panel at ICC, there isn't a solution out there right now that's compatible with our technology stack (and without significant non-technical drawbacks).
I already said I was on board with this capability! But the fact remains - for at least 90% of our users, Perspective as it is works well enough and offers enough functionality for them to accomplish what they need today. Everything we bundle into the platform or a first-party module like Perspective has to be supported more or less forever. There are absolutely use cases for "power users" like you, who are over-represented on this forum. Joe and Jane Doe working in a small factory have no use for those advanced capabilities. We have to try to cater to both audiences at the same time. Right now, the way we cater to power users is the module SDK.
Like I already said, I could see an enhancement to the Webdev module that made it easier to integrate custom JS with Perspective - that would be an olive branch to folks like you who want that extra power and flexibility without overwhelming "regular" users.
JS is not faster than Java. It is probably faster than Jython. But with things like WASM GC support getting integrated into browsers, it's possible there's a future where we can deliver a single compatible scripting language that works in Vision, Perspective, and on the Gateway. That's absolutely a better deliverable than telling end users they have to learn a third programming language to use Ignition.
This isn't a technical limitation. We're fully aware of how we could expose Javascript, authored in the Designer, onto Perspective pages. This is a business limitation - we haven't seen an argument compelling enough to make it worth the significant uplift required in: 1. our support department, 2. our training department, 3. our sales department, 4. our QA process.
I like this blog post a lot: