News for hackers. Stuff that matters.

A comment on Godot is not the new Unity – The anatomy of a Godot API call. Parent comment

Re:Godot is not the new Unity – The anatomy of a Godot API call by Lucasoato on Monday September 18, 2023 @06:09PM (#37562777)
They should remember that even Unity had to deprecate the Boo language to go forward :)
[ Parent | on HN ]
Re:Godot is not the new Unity – The anatomy of a Godot API call by dandellion on Monday September 18, 2023 @06:30PM (#37563017)
Not sure Unity is a good role model...

Also, having used both Boo back in the day and GDScript in Godot more recently, I'd say that one big difference between the two is that Boo was really bad, and GDScript is actually pretty good.

[ Parent | on HN ]
Re:Godot is not the new Unity – The anatomy of a Godot API call by eddythompson80 on Monday September 18, 2023 @06:32PM (#37563043)
What's wrong with Unity from a technical prospective not marketing/business prospective?
[ Parent | on HN ]
Re:Godot is not the new Unity – The anatomy of a Godot API call by cfgyuiikhg on Monday September 18, 2023 @09:34PM (#37564663)
It was fat and glitchy from the get go.
[ Parent | on HN ]
Re:Godot is not the new Unity – The anatomy of a Godot API call by johnnyanmac on Tuesday September 19, 2023 @05:20AM (#37567384)
Unity got a stigma for delivering half baked features and dropping support for existing features without a replacement. The epitome of this was where in Netcode, where I believe they had no officially supported solution despite the engine having 2 different packages which were both half-baked, all while the DOTS variant was far from release.

I don't think Godot should go that route.

[ Parent | on HN ]
Re:Godot is not the new Unity – The anatomy of a Godot API call by mattigames on Monday September 18, 2023 @06:25PM (#37562957)
Both Boo language and UnityScript were deprecated (the later was oftenly mislabeled as JavaScript, creating quite a confusion between newbies)
[ Parent | on HN ]