# Exchange Resource to use Javascript with Perspective

**URL:** <https://forum.inductiveautomation.com/t/exchange-resource-to-use-javascript-with-perspective/81937>\
**Category:** Ignition Exchange\
**Tags:** perspective\
**Created:** [November 15, 2023, 5:05pm UTC](https://forum.inductiveautomation.com/t/exchange-resource-to-use-javascript-with-perspective/81937 "2023-11-15T17:05:47Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [November 17, 2023, 4:33pm UTC](https://forum.inductiveautomation.com/t/exchange-resource-to-use-javascript-with-perspective/81937/19 "2023-11-17T16:33:30Z")

</div>

> [@nader.chinichian](#):
>
> I hope in 8.3 instead of Ruby or GO language we have Javascript.

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).

> [@nader.chinichian](#):
>
> Also, I believe if IA opens this capability, the dev team doesn't need to add more components to Perspective and they are free to do better things as people themself can create new components and functionality and share it in exchange.

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.

> [@nader.chinichian](#):
>
> JS is faster, and it run on the client side, and give a lot of amazing option to the user which is not possible in other scripting language.

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.

> [@nader.chinichian](#):
>
> May be reviewing other platform solutions for this can help IA to add this functionality into the Persepctive.

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:

> **[Negative 100 Points - Strongly Emergent](http://stronglyemergent.com/blog/2013/negative-100-points/)**
>
> A short post by Eric Gunnerson about designing C#, nearly a decade old now, has stuck with me for a long time. \[the question\] implies that we started …

---

_[View the full topic](https://forum.inductiveautomation.com/t/exchange-resource-to-use-javascript-with-perspective/81937)._
