magic_lobster_party @ magic_lobster_party @kbin.run

Posts

1

Comments

624

Joined

1 yr. ago

Faster compilation is probably nice, but making a new language with all its tooling from scratch is a huge endeavor. Props to him for actually doing it.

The problem is that all this work takes away time from the actual game development. I’m not sure about the scope of his next game, but from what I’ve seen I don’t really understand why his Sokoban adventure game can’t be made in Unity. I don’t think he’s pushing any hardware limits with it.

Unity also got hot reloading nowadays, which is about as fast iteration you can get.

I’m just armchair guessing, but I believe he would’ve been done with his game by now if he just used Unity.

There’s no evidence of the contrary either.

No, that’s just bloat feelings

I’ve seen things you people wouldn’t believe.

His arguing hasn’t helped him to maintain is image either. It’s hard for me to respect the guy, which makes me less inclined to buy his games.

Or just test the damn thing before shipping it to customers. That’s standard practice in the software industry.

If they had just installed it on one of their own Windows machines, none of this would’ve happened.

The point about the Bechdel test is that it’s such an incredibly low bar, and yet most fiction fail at it.

Yes that can be true, but fun doesn’t pay the bills.

Jonathan Blow has been more interested in marketing his niche programming language than his games, so maybe that’s why.

Risks are normally outside the reasonable control of the company. For example, sales not hitting the target. They can’t just press a button and up goes the sales.

This was entirely within the company’s control. That risk shouldn’t ever be there at all. They could’ve avoided the entire situation if they chose not to ship the faulty software.

Naturally there’s a drop in profit in a year where they don’t release a heavy hitter like Elden Ring. And the numbers don’t include the sales of the expansion.

I’m sure they have their finances under control.

I believe it was a desperate attempt to get a new source of revenue. His upcoming Sokoban game is taking forever to make, so it’s not going to bring them any new revenue anytime soon. In large part because he made the arcane decision to create a new programming language for it (as a replacement for C++), because apparently Sokoban is the type of game where you really need that high performance.

Haven’t properly watched the videos, but I don’t think OOP is that bad. I even think encapsulation is one of the core strengths of OOP.

I’ve worked with systems where no thought was put into encapsulation, and those are often incredibly difficult to work with because everything is heavily interconnected. Can’t make a change in a small thing without risking breaking something else at the other side of the program.

I like to see encapsulation as a workspace. It defines the tools we have direct access to. Changing one thing in a workspace shouldn’t affect anything on the other side of the program. Makes it much easier to collaborate in large teams. Minimizes the risk of interfering each other’s work.

There’s pride in all sexualities

I think applying design patterns blindly without understanding what problems they’re supposed to solve is often more harmful than not using them. It can lead to difficult to manage code bases because the program is over engineered for problems that don’t exist.

My general rule of thumb is to write code that can be easily adapted to unexpected changes in requirements. Avoid writing code that paints yourself into a corner. Simple solutions are often easier to work with than complex solutions. If what you’re doing adds a lot of complexity, take a step back and seek other options. Maybe you’re overlooking an obviously simple solution to the problem?

I think inheritance almost always has this “painting yourself into the corner” tendency. Once the design is set, it’s often difficult to break free from it. Composition along with interfaces is generally the better choice. Often not even interfaces are needed.

This comes with experience. You learn what works, and what doesn’t. Often you do it the hard way.

Databases are tricky. I have no good advice for that.

He’s also probably doing “altruistic acts” to defend himself against criticism.

Ow my balls!

65 years: "What is ski bidet toilet?" 65 years: "Yes SKIBIDI TOILET!!!"

7 years: "Yes SKIBIDI TOILET!!!"

I use ash btw