Their suggestions AI is quite a bit behind Spotify's unfortunately. Dunno if that's by a lack of design or because of Apple's privacy stance -- probably the former.
Use < and > for numbers and strcmp for strings. A strict type > would be very weird because besides returning TRUE and FALSE it'd need to throw a TypeError, I guess?
>A strict type > would be very weird because besides returning TRUE and FALSE it'd need to throw a TypeError, I guess?
Yes, which would make it behave exactly like probably every language with strong runtime typechecks. Very weird indeed. It's obviously much more preferable that the code sometimes does the wrong thing without warning.
And of course with static typing, it would be extremely weird since the code wouldn't even pass the compiler!
Those who have a monthly mortgage payment of $9000. Substract $500 (or more if the government doesn't help you with their costs) for each child in your household.
ECS is the "microservices" of game development : it's touted as the way to go, and in some cases it's the best solution, but it comes with increased wiring complexity cost, and the hype surrounding it causes it to often be adopted for dubious reasons (e.g "deep class hierarchies are bad, therefore I need ECS").
ECSs are sort of designed to be flexible and make it easy to extend and mix the behaviors of a game. Most games do not need such flexibility, because professional games are designed and you already know what capabilities are needed, and it is more efficient and less complex to implement those things directly.
However, if you're designing an open-ended game engine for other people to develop in, then an ECS is a godsend, because you have no clue what they plan to make their game do.
Their suggestions AI is quite a bit behind Spotify's unfortunately. Dunno if that's by a lack of design or because of Apple's privacy stance -- probably the former.