So what are the ideas? Are they anything? Not really. What they are is an exploration of the things that can happen when you’re in a simpler version … - Jonathan Blow

If what you're objecting to is the flavor and attitude and the nature with which Casey was expressing his criticism, then there's a little bit more of a point there, however, again, you eliminate that at your peril. It is well-known that many of the greatest contributors to society—not just in software, but in all science and technology and the arts everywhere—many of those people have been hard to work with for one reason or another. And partially it's because they care tremendously about what they are doing. They care tremendously about the form in which they are working. You might say "oh but that guy doesn't need to be crotchety and mean about that thing", but you can't take away that part of the personality and have everything else, because that part of the personality is quite likely an integral part of what made the rest of the artist or the scientist as good as they are. You can't just decide "Albert Einstein should have had a different personality but he should've still done all the cool relativity stuff and figured all that out and then I'm going to sit on my couch and eat Cheetos and I'll criticize Einstein for not being a good person in some certain way that a hundred years later I decide is the right way to be, but I will take all the stuff that he contributed because it helps me eat Cheetos and that's great". That is so—it is important for us to see that kind of lazy, bloated, fat, social criticism of others as being as toxic as it actually is, and as being as unproductive and decay-inducing as it actually is. That's way more toxic than a programmer saying angry things—that kind of criticism, because that kind of criticism that's in vogue in places like Twitter right now at a large scale will destroy human society, whereas the crotchety programmer thing on a large scale built a large part of the human society that we have right now. So be very careful with that stuff, and on my part, I feel that one of the better contributions I can make is to not tolerate that kind of criticism. I just won't put up with it. If you come to this channel with that kind of thing I'll just ban you because it's stupid and I don't have time for it. There's too much of it. It's cheap, all it is is posturing so that the person making the criticism can feel better, can show other people that they are a good person, and it's gross, it's really gross. And it's destructive. We don't need it.

People have this reaction, ‘Why would I be interested in a game where you just walk around and draw lines on a bunch of panels? Why is there even a world there? Why is this not just a cheap iOS game or something?’ There are very good answers to that, but you don’t want to give people those answers because you then spoil the game for them.

As you get a game closer to done there are more graphical assets, and they get bigger and bigger and it takes longer to do things like load them or process them if you need to do some automated processing on them or recompute the lighting for the world, and it gets to a point where it becomes very sluggish to just try to get new things done and that was a real drag. And it's especially a drag when there's so many things to do and you feel like you can't do them very fast because of the computer. And part of that was programming in this programming language C++ that most engine programmers use to build things with, and I just had this very fatalistic attitude toward it like "Well... we can't do anything about that so I just have to like deal with this and get the game done". And then at some point I just changed thatI was like "Wait, is that really true? I know that that's what everybody thinks but is that really true?" And I was like "Yeah, no, it's not true". Like "I shouldn'tlike, we should finish this game in C++, but I don't have to accept that this is what I'm doing for the rest of my life. I can actually change this and do a different thing", and that's what led me to work on this new programming language. But as soon as I decided to do itas soon as I said "This is actually not an unfixable problem; we can do something about this", I became much happier, immediately, because I was no longer in jail; I was no longer in C++ jail for the rest of my life. So I try to use that as an example for other things as well. WheneverI know that feeling now; I know smaller versions of it, like when it comes to the way a game is designed, like "Oh, I realize I'm having this 'I'm in jail' feeling like I don't like this part of this game's design, but I've assumed that it just has to be the case." And I just go back and look, "Does it really have to be the case? Well, I mean, I decided that because this but we could make that decision differently if we're willing to pay the cost of making the decision differently. Is that cost worth me being happier with the game because it's a better game? Well, yes." So once you learn to revisit those decisions it becomes a very good thing to do and so that C++ instance I think was the biggest one, but I've learned to do that more often from that example.