Pretty sure its Pixi.js

+1 for this display. Absolutely beautiful picture quality, colors, and not glossy.

Don't overlook p5.js ( https://p5js.org/ ), a Javascript library built around the concepts of Processing, built with support from the Processing Foundation and NYU ITP.

As an owner of one of these machines, the Touch Bar is fairly gimmicky. There are a couple of use cases that are nice. Brightness and sound adjusting being tied to a slider for instance. For the most part, it's cumbersome and time-consuming to use. I'm almost entirely a keyboard user and do not take my eyes off the screen. Even with the proximity of the Touch Bar to the screen, shifting my gaze downward requires more effort than I thought. The esc key not being hardware sucks, it's also slightly off in its placement so it requires me looking at the touch bar making sure I'm actually tapping it as there is no response mechanism. I'm open for the potential to be surprised, but at the moment its a gimmick.

It is, some extremely talented people put in time there.

We've been using this in Beta for a couple of months now. Inspect is finally at a usable state. Keeping the discussion, iteration, and handoff processes between our Design and Engineering teams to one platform has been a fantastic experience so far. Speed improvements have really made it worth its while and now Sync also supporting Inspect'able artboards is a game changer.

It's a displacement technique implemented in WebGL with shaders. Here's a writeup on explaining some of the principles and some other techniques around generating geometry and noise. https://www.clicktorelease.com/blog/vertex-displacement-noise-3d-webgl-glsl-three-js

A-Frame builds on the WebVR API and Polyfill, it's not meant to be built for specific devices. They've built the framework to support any new upcoming devices. Since this is all open-source and community driven, it will take time especially when these devices are still in relative obscurity and cost quite a bit. HTC hasn't done any work on contributing how the devices should support these existing APIs (that are still quite in flux), which would be an awesome contribution to the community.

I appreciate the effort Adobe has put into the project to address the evolving needs of interface designers, albeit quite late. This is a radical step for Adobe for sure. Not utilizing the existing cross-platform frameworks and conventions from existing CC apps is a huge departure.

It's buttery smooth, granted there isn't much there yet. If it weren't I'd say that Adobe should abort the project. It's hard to make judgments about it yet because so many core features aren't there. While it's easy to imagine what Gradient Fills or Symbols might do, it takes a little more work to imagine how they'll be implemented into the framework there.

I'm a little puzzled by how light this preview release is. The videos last year that came out showing off Comet seemed as if they were way further ahead than this. What's the deal Adobe? When will a real feature filled version be shared?

I got to play with Tiltbrush for the first time yesterday. I'd say it's the leading example of HMD experiences. It is not yet far along enough yet for real-world applications, but it easily triggers you to imagine how these types of interactions could be used for practices.