If you’re being objective about a programming language, its strengths and weaknesses are always going to a reflection of the game you’re trying to make. Python’s ecosystem will get you very far making web services, but less so with cert on consoles.

C# and GDScript are no different. They both have made design decisions for particular reasons.

You’re a skilled developer in real languages, so I’d encourage you to explore why other developers might prefer a DSL for their needs!

My philosophy has always been “ergonomic scripting or drop to C++”, so I’m quite okay with it.

C# has always felt a bit clunky to me. It’s nice to have alternatives.

I tried the 7DFPS Game Jam this month, trying to learn a little more 3D modelling, as well as Godot. It was my first time using the engine to produce a HTML5 build.

https://danbolt.itch.io/7dfps-2025

Within the scope of a game’s production, the programmer time spent dogfooding the new audio format can be used towards something else that improves the value of the end product.

The uncompressed audio for latency-sensitive one-shots usually isn’t taking up the bulk of memory either.

> programmer time spent dogfooding the new audio format can be used towards something else that improves the value of the end product

Like exploring the 'widely accepted industry practices' and writing code to duplicate the assets, then writing the code to actually measure what it did what the 'industry practices' advertised and then ripping this out, right?

And please note what you missed the 'if it really bothers you'.

The last studio I worked at where the Steam Deck came up, the rendering lead muttered “ew, no! we don’t have time to figure that out!” and that was the end of the conversation.

A week after launch, the Proton devs pushed a hotfix and the binary’s been compatible with Linux ever since.

The Nintendo 64 has a z-buffer, but the slow fillrate means that depth-checking can hamper your frame time. World Driver Championship sorted their polygons PS1-style with unique microcode, and got a very nice framerate.

I sometimes wonder what the Nintendo 64’s library would have been like if they had sorted polygons on the CPU like other consoles of the era.

I don’t know if I could list something that matches say Cuphead or Silksong, but I do think that Godot is currently on a Clayton Christiansen-style worse-is-better ascent right now.

When my parents had a house built in the early 2000s, my father was adamant that Ethernet should be wired to every room. It seemed like a good way to future-proof the building for the 21st century at the time. The year we moved in, tweenage me asked about connecting my Nintendo DS to the internet in order to play Animal Crossing online.

I wonder if we would have done the Ethernet again if he knew that Wi-Fi was going to become so common.

> I wonder if we would have done the Ethernet again if he knew that Wi-Fi was going to become so common.

Today, if your wiring up a house you put ethernet drops everywhere.

POE is a thing, and it's getting more popular.

Cameras, blinds, MM wave... It's almost to the point where one should be putting a media box in every closet as a mini wiring hookup.

Close to the floor as well as close to the ceiling.

Even with wifi, big houses or tough RF environments need mesh units to get ubiquitous wifi coverage. And there, ethernet wired backhaul is far, far superior to wireless. So maybe your dad was prescient in a different way.

The issue with wiring your house for Ethernet is that 2003-era Cat5 that a random builder or DIYer grabs from Home Depot isn't going to carry nearly as much as the Cat6A cable you would want if you need the cable plant to have a chance of keeping up with network capacity growth. But that needs quality installation.

I had a fairly extensive Ethernet and audio speaker setup in the course of a couple of house renovations. Much of that is trashed from smoke mitigation after a kitchen fire. Will pretty much just use WiFi from here on out.

Ethernet in each room remains valuable for other reasons, such as set top box devices, etc.

The issue wasn't whether wifi was going to become so common, it was the guaranteed improvement in reliability and speed of wifi.

Anyone could use ethernet, and still can.

I would still do this in 2025, just with different category of ethernet cable, that's it.

Ethernet in each room remains valuable for other reasons, such as set top box devices, etc.

I’ve lived in places where they’ll add the bike path during scheduled road work, as it’s cheaper to get it done while there’s a crew already onsite. It can be a bit stochastic at first like you mention, but over a while I’ve seen the corridor eventually fill out, making the most of a shoestring budget.

Perhaps something similar where you live?

One of the screens on the Vancouver SkyTrain platform crashed once and displayed the xfce logo, which made me feel a bit of excitement in wondering how it was implemented.