# ES6 version incoming

**URL:** <https://forum.babylonjs.com/t/es6-version-incoming/446>\
**Category:** Announcements\
**Created:** [December 26, 2018, 3:29pm UTC](https://forum.babylonjs.com/t/es6-version-incoming/446 "2018-12-26T15:29:26Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![Wingnut](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/wingnut/32/53_2.png) [@Wingnut](https://forum.babylonjs.com/u/Wingnut)\
**Post date:** [January 10, 2019, 4:41pm UTC](https://forum.babylonjs.com/t/es6-version-incoming/446/19 "2019-01-10T16:41:55Z")

</div>

Yeah, I understand that, even though I often forget that. 🙂

Hijack code into playground… that is ONE subject… and I use it heavily for troubleshooting core issues. Don’t need to, but handy.

Now, if you mean hijacking our own version of Oimo and maybe renaming it and glue-coding it into backward compat… that is ANOTHER thing. That is a DIFFERENT kind of “hijacking” heheh

But, weirdly, Deltakosh’s comments… apply to BOTH kinds of hijacking.

How did he DO that? haha. New thread, same topic: [The Future of OimoJS in BJS](https://forum.babylonjs.com/t/the-future-of-oimojs-in-bjs/675)

Something “feels good” about BJS Inc… just blatantly “running-with” its own version of Oimo. hmm. See the new thread… for more, and to pummel Wingnut as bloody as you wish. heh

---

_[View the full topic](https://forum.babylonjs.com/t/es6-version-incoming/446)._