He's acknowledging that these people had to do things wrong, at least in the sense that they had climb a steep learning curve and deploy a heavyweight system, because they basically had no other choice. He's describing the gap that he saw that motivated what he demonstrated. Those artists aren't going to be offended that he attacked their deep love of Unity, they're going to be happy that they have an alternative that suits their needs.
We differ in what we think is "wrong." I would say that your definition of wrong is the least interesting to the people who are currently using Oculus with e.g., Unity. They don't really care about the same things you do.
> had climb a steep learning curve
It's not that steep. I mean, they're not hardcore engineering types, and they figured it out right?
> and deploy a heavyweight system
Is it that heavyweight? Does anyone really care that it's a 16 MB executable? Did that get in the way of anything other than the App Store's arbitrary 50 MB limit? Does performance really matter when you're drawing a panorama?
Define heavyweight. For many people, opening a command line is heavyweight. You're not appreciating how nice Unity is.
> they're going to be happy that they have an alternative that suits their needs.
Time will tell. The history of art tooling is complicated. Maya nee PowerAnimator has been around since 1990. Pixar, which thought it had a better way of doing things with an alternative universe of tools, uses it now too. Photoshop, MediaComposer, Flash, Unity... Everything has its own history and its own outcomes.
I don't know if any of us are equipped to predict what is the right way to develop for the platform. That's not what I'm saying. I'm just saying he's being kind of a jerk and has a condescending attitude towards people who are actually delivering things with Oculus.
* you can't load it without a long unity splash screen without paying $3K for a pro license
* it renders photospheres poorly - no dynamic eye buffer resolution or separate overlay compositor support
* based on your overall attitude/taking offense, I'm going to assume you haven't actually used Unity at all. Try to HTTP stream/lazy load web assets, go ahead. Also go ahead and try to build links in Unity, or to load JSON. (Hint, none of those are available out of the box). Now try to make changes/iterate, or distributing your changes to clients. Unity is a huge pita.
Honestly, I can't understand why you are arguing online about what's "wrong" or not about something you obviously haven't tried and know nothing about. Now, that's offensive.
What is meant by "wrong" here is "this is more work than it should be to accomplish the desired result...so let's create some infrastructure to make these types of things simpler"
If he meant what you said, he would have just said that.
Perhaps my ears are biased here, as I (as a programmer) have a great respect for "media people" due to their skills in content creation which I myself lack. "Content people" is the other term he uses here. What good is an engine without content? Different skills, not one greater than the other. I seriously doubt that John Carmack was attempting any sort of comparison here, subconsciously or not.
My take, as paraphrase: "It seems like using Unity is a lot of overhead for a panoramic VR slideshow. Here's another tool that you can try out and see if it meets your needs."
But obviously someone who has the technical knowledge to program video games (slight as that actually is...) IS in a completely different ballgame from someone who, say, is trying to get rich by streaming on Twitch or making a content farm on Youtube. I find that to be a valid usage of the phrase "media people."
As VR takes off, there will be a valid distinction between people who are using it more or less exclusively for purposes like content farming and marketing and people who are using it to build games or worlds of more depth than "look around this 3d photograph" or possibly "click the monkey." It's a valid distinction.
John Carmack(from the video): This is in now way replacement for highly sophisticated apps... ...you should clearly be using Unity or Unreal, you should be using a real game engine. If you have to do a lot of interaction with Java or native code, you should be writing a native application.
That mentality sort of bodes poorly for Oculus. Of all things to say, why does he have to open with, essentially, 'The people who are actually getting things done and most excited about my platform are doing things wrong. I'm going to tell them they're doing things wrong, and then I, who haven't released a game people wanted to play in years, will show them how they should be doing things.' It's the opposite of inspirational.
I know he's a phenomenal programmer and all. But he's such a blowhard. There are lots of blowhards behind all sorts of platforms, but usually those platforms have so much momentum that the platforms grow in spite of the blowhards, not because of them. Nobody is using Oculus. Facebook really nervous to specify the number that were sold. [0] And this guy right here isn't helping.
And before you downvote me into oblivion, I'm mostly commenting on his condescension. VRScript will be useful to someone, like many tools out there, and I'm glad he's working on it. But his language like "media people" isn't so easily ignored as an advocate for the platform and a representative of the very best of engineering.
If you're at Facebook in charge of this stuff, you should take a close look at this sort of rhetoric.
[0] https://www.dropbox.com/s/s1fo7069mbokcc0/Screenshot%202016-...