Mario Zechner
Fuchsiii~~~@badlogic remindes me of that one big studio that proudly worked in rust for years but they droped it once their game moved to consoles. No console company is providing a rust compiler so they had to maintain the compiler and std library port themselfs.
@fuchsiii Chucklefish iirc. I think exploring new tools is super valuable, even if you return to where you came from. Usually, you'll have a new perspective on your old state of affairs.
Console access for anything not sanctioned by the manufacturers has always been pain. See Godot,
Kevin Karhan 
@badlogic @fuchsiii Granted, @godotengine does get a workaround via #W4Games providing the sanctioned, invite-only #Console #DevTools for them, similar to #Unity3D, @defold and #UnrealEngine...
Granted, the locked-down nature of #GameConsoles is part of the "Razor & Blades" model they use...
Zoidberg For President@badlogic That is one terrible screen grab...
Ölbaum@badlogic @grumpygamer People have been talking shit about Objective-C for decades, but retain/release/autorelease and associated rules are easy to understand and apply.
@oscherler @grumpygamer all languages are beautiful!
Olivier Groulx@badlogic I almost screamed at the point about UI. It seems like no one understands that game UI has specific constraints and requirements.
The last thing I want for game UI is Chromium. I want Flash.
Daniele@badlogic nice read, I enjoyed it. The only thing I'm not sold on is the concept that a game (indie or not) is fundamentally different from another development project. I've been doing both gamedev (in my spare time) and android dev (for the past 10+ years, professionally), and requirements change all the time in both.
I feel a lot of game developers lean on this difference to excuse lazy code/throwaway code, and imho that's more damaging than anything. 1/2
@badlogic I think clean code actually enables development velocity (not talking about Rust, as I mostly develop in jvm languages). It also helps with the game stability, like not crashing all the time, or no random corruption of saves, which is something I often saw in not properly structured codebases (games or not). Same goes for tests which would help a lot with giving confidence in making significant changes to the code
Robin@badlogic This whole article seems to point at a larger issue in game dev information. See, 99% of developers never ship a second game. They ship one, it flops, and they leave the industry.
That means that the majority of discussions, tutorials, even whole game engines are made by people who have never shipped a game before.
As a result, there’s a very low signal to noise ratio in game dev resources. It can be tough to filter that.
@Robin_Van_Ee good observation!
André-LA 🎀 gamedev@badlogic “The community as a whole is overwhelmingly focused on tech, to the point where the "game" part of game development is secondary”
This isn't exclusive to Rust, but any community made around a tech where using that tech is the main goal
This is in my opinion the main argument behind "game engine developers should be game developers first", otherwise you get these next-gen engines capable of making AAA graphics... and anything else
Turns out games comes from game design, not tools