VeeSilverball

Some of my own thoughts, which rebut the article in parts:

1. Godot does have "barbell performance" - you can make it go fast if you drop to C++ and do low-level engine things to add new nodes, resources, etc. You can also make it go fast when you use the premade nodes without a great deal of script in between(and the nodes are, FWIW, pretty flexible and composable). What it doesn't do at present is the thing Unity users are used to, which is "fast scripting". Fast scripting still means working around the garbage collector and the overheads of going between native and a runtime. C# is a kind of flytrap for the needs of high-end games, and Unity has only seemingly surmounted the issues by doing a lot of custom engineering for their use-case. That is, you don't really code standard C# in Unity, you code Unity's C#, which is nearly as bespoken as GDScript.
2. Saying the engine is coded in a naive way is actually not as smart as it seems, because there's a maintenance cost to always doing things in exactly the most optimal way. The target for what is fastest changes every time the platform changes. As a (up until recently) relatively small project, it's overall better that the engine stay relatively easy to build and straightforward to modify, which is what it's done. The path it's taken has helped it stay "lightweight". The price of that is that sometimes it doesn't even take low-hanging fruit that would be a win for 90% of users.
3. The 3D in Godot 4 is capable of good test scenes, but everyone seems to agree that it's not really ready for production for speed reasons. Any specific point on this just backs that up. And that's disappointing in one sense, but pretty okay in others. If you need high-end graphics, Unreal will welcome you for the time being.
4. On that note, developing for console always comes with fussy limitations, at minimum just meeting TRC/TCR/lot check; that's why professional porting is a thing. Engine devs usually end up in the position of maintaining these multiple-API abstractions because it's necessary for porting. It's the same deal with the audio code, the persistent storage, the controllers, the system prompts, it just goes on and on like that. So, rewriting the rendering bindings to do things in the D3D way and not the Vulkan way is actually a bit of a whatever; it's more rendering code. It changes some assumptions about what binds to what. But it accesses the same kind of hardware, running the same kind of shaders. A lot of ports in the not-so-distant past basically had to start over because the graphics hardware lacked such a common denominator.

The author's bio says that they have been doing this as a professional for about 5 years, which, face value, actually means that they haven't seen the kinds of transitions that have taken place in the past and how widely game scope can vary. The way Godot does things has some wisdom-of-age in it, and even in its years as a proprietary engine(which you can learn something of by looking at Juan's Mobygames credits the games it was shipping were aiming for the bottom of the market in scope and hardware spec: a PSP game, a Wii game, an Android game. The luxury of small scope is that you never end up in a place where optimization is some broad problem that needs to be solved globally; it's always one specific thing that needs to be fast. Optimizing for something bigger needs production scenes to provide profiling data. It's not something you want to approach by saying "I know what the best practice is" and immediately architecting for based on a shot in the dark. Being in a space where your engine just does the simple thing every time instead means it's easy to make the changes needed to ship.

To get the initial federation going, some kind of "subscribing" action has to take place, e.g. following a user.

Coming soon: rebranding /r/piracy to "pirate cosplay"

One direction to take this conversation is to legitimize a formal ads platform and move the technology in that direction. It's not a concept that has had airtime in federated social(open source, anti-corporate and all) but it fits into the model of enthusiast communities to have a magazine that is "both articles and ads".