tacotacotaco

I was generally frustrated with the parade of posts about how bad Godot is from former Unity devs. This happened to be the article that I commented on.

I appreciate that the author crossed out his suggestion to remove gdscript vs removing it. I will give him credit for transparency. That doesn’t negate the original intent.

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.

I am so glad that Juan et al are leading Godot and not me because frankly I would be offended by all of this. It hasn’t been a week since the Unity fiasco and all I see is post after post from people complaining that Godot isn’t c# enough. This is like showing up for dinner and insulting cooking before you’ve even tasted the meal. There are definitely opportunities to improve Godot but there are more constructive ways to contribute than drawing a new floor plan for the house on the table cloth while the first course is being served.

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#.

How many users that are happy with gdscript are taking time to read vote in a GitHub polling posted about c# issues?

True, acid rain was not caused my lead but there was public and industry resistance to requiring all vehicles use catalytic converters. Lead had to be removed from fuel because it corroded the catalytic converter. It was chaotic for several years but the car industry was able to make it work. The market didn’t remediate acid rain, regulation did.

I only hobby in game dev. I have read some basics of ECS and IMO it seems a lot more intuitive than the “normal approach”. I think this is a case of using familiar tools we are comfortable with, not necessarily better. Unity’s ECS implementation is a hot mess though. I am looking forward to seeing what Bevy delivers as it matures.

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.

Human civilization made it all the way to 1990’s without commercial internet. Maybe keeping children off the internet would make them better prepared for society.

Not the OP but I do run Teams on Apple Silicon and it is still a bug-ridden mess. Crashes, rendering bugs, file attachment bugs. At least once a week, usually more. Searches fail to find results that I can manually locate by scrolling through the chat history. I have reinstalled the app more than once.

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.

I am not against types but I do find typescript’s type system to be deficient. Additionally, functional programming is not incompatible with type systems but typescript’s type system in particular makes it more difficult.

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 completely forgot about those trays. Yuck!