I am aware of the part about how this affects bindings for all languages. My point still stands that this is premature optimization. The author even admits, “In some projects 95% of the CPU load is in an algorithm which never touches the engine APIs. In that case, none of this matters.”

So again, if this is about performance then why not remove c# as well? If we’re to “tear it all down and start again” we might as well do it in rust. Oh? If I want a rust game engine I should look at Bevy. Is saying that really a second “wrong”?

I don’t have anything against this author specifically. I respect that they did more than simply look at the showcase screenshots to make their assessment. My initial comment was more a general expression of frustration with the prevailing attitude on various forums. I like reading r/godot to see individuals creating games, not creating grief. (Frankly, I found the Unity memes to be a bit mean spirited as well.) I acknowledge my initial comment did nothing to remedy the situation but I was tired of hearing it. I have since stopped reading that subreddit. Enjoy your c# crusade.

No, I was criticizing premature optimization. I explicitly stated “there are definitely opportunities to improve Godot”. I took offense to devs joining the community and nearly immediately proclaiming ‘this is all wrong and you have to do it my way.’ Well, if it’s not right for you then move on, thanks for visiting.

If we’re to be so focused on performance then why not ditch c# also and only use c++ or rust exclusively? Better memory utilization, better processor performance[1], and no more garbage collection stutters. Oh right, it’s not your preferred language.

I’d rather we all just make games instead of fighting language wars, but seeing so many of these posts in the last week makes the community feel hostile.

[1] https://programming-language-benchmarks.vercel.app/rust-vs-c...

Have you even made a small game with gdscript? If Godot doesn’t meet your needs then there are dozens of other game engines to choose from, some are native c#.

Another fun fact, the Unity CEO and several board members sold some of their stocks a few weeks ago. [1]

[1] https://kotaku.com/unity-developer-fee-installs-john-ricciti...

I agree that copying an existing product will be easier and is usually cheaper and more performant because you can leverage your competitor’s R&D and lessons learned. I presume this is why some tech companies’ product lines are full of clones.

I have shared these observations in their feedback pop ups and I know Microsoft loves collecting telemetry. Why should they dedicate more money/resources to fix defects when it clearly hasn’t stopped them from growing their market share?

Teams is the first example I use to begrudgingly explain to someone that quality doesn’t matter.

Several of the terrible typescript projects I referred to still used property values to represent state (like your example). Just because every definition has a type doesn’t make it good code. Shitty typed code is still shitty code. My concern is that many in our industry conflate typescript with quality and stop there.

I have worked on multiple typescript projects that had terrible code quality. Types do not make you write SOLID code.

I find functional programming and well-used functional patterns do result in higher quality code. Typescript’s type system makes writing functional code more difficult. The documentation even recommends against it[1].

IMO typescript is easy to prescribe as a panacea, “just use typescript”, whereas understanding how to write SOLID code takes time.

[1] https://www.typescriptlang.org/docs/handbook/typescript-in-5...

[1] https://en.m.wikipedia.org/wiki/Joel_Kaplan [2] https://www.wired.com/story/facebook-joel-kaplan-washington-... [3] https://www.wsj.com/articles/facebook-algorithm-change-zucke...

https://www.wired.com/story/deep-sea-mining-electric-vehicle...

https://www.wired.com/story/unbelievable-zombie-comeback-ana...