Archived - Why the Changes for JavaScript* with the Intel® RealSense™ SDK?

By Eric M Mantion, Published: 05/19/2015, Last Updated: 05/19/2015

The Intel® RealSense™ SDK has been discontinued. No ongoing support or updates will be available.

At the risk of sounding a little bit like Master Yoda, Transparency leads to Openness; Openness leads to Trust; Trusts leads to Togetherness; Togetherness leads to Community. In that spirit I’d like to go over some changes in the new release of the Intel RealSense SDK with plenty of advancements and updates.  However with that we are making some adjustments to how we distribute and package the JavaScript support with the SDK.  This post is focused on providing clarity around that for our JavaScript developers.

Specifically, with the latest release (Build Number:, May 2015), if you want to continue to develop using JavaScript, you will need to install a separate package that will be listed on the download page and will be easily accessible. The short answer for why we are doing this is a fairly simple one: it is a technical issue that will cause unfavorable results if you deploy a JavaScript-based web solution to certain browsers due to a security issue that had been solved but said fix has affected our JavaScript components.

To be clear, I would like to emphasize two things:

1.   We are well aware of the issue and its solution will be a major aspect in the very next release of our SDK, to come out this summer

2.   This temporary situation should NOT be taken, in anyway, as Intel backing away from JavaScript — we continue to be staunch advocates of JavaScript, HTML5, and other, similar, open web standards

To be a little blunter, we are very aware that some of the best, "game-changing" usage models for RealSense will be through the web browser. While online sales have continued to grow strongly even during a global recession, there are still some gaps in its usage, especially when it comes to sizes and dimensions. Case in point for me, last year, when I bought my first motorcycle, I knew I needed a helmet. Thanks to my time in the Navy, I knew my hat size was a 7 ¾, but motorcycle helmets come in S, M, L, XL, etc. In the future, I could have, in that situation, just go to the helmet company's website, they could access the Intel RealSense camera in my computer, scan my head and tell me my helmet size. The same concept works for eye glasses, shoes, suits, who knows what. Plus, there could be an even more interested paradigm coming where I scan my torso, then some robot tailored could stitch me a near-custom suit. In the future, when ZZ Top sings about a "Sharp Dressed Man," it could be due, in some small part, to Intel RealSense technology.

So, there you have it, in a nutshell (or TL;DR for you Reddit fans out there):

  • Yes, this release of the RealSense SDK will be slightly less convenient for JavaScript developers
  • No, this is not being done for some secret "we hate JavaScript" reason, but rather a very specific technical issue which we are working hard to fix for our next release
  • Yes, the next release of the SDK will have JavaScript baked right in the way it has been before
  • Yes, we realize JavaScript is a very popular and useful language that is the engine of the Web

Product and Performance Information


Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804