This looks like a lot of complexity up front with no foreseeable payoff.
Why are we implementing a whole dynamically allocated stack for states before doing anything domain specific?
How many states could you possibly be expecting to have in a full game? 3? 12? 100? The examples of states were like the menu, action screen, and pause screen. So it sounds like very few. Drop the realloc'ing and free'ing and just statically allocate N states and be done with it. Save this complexity for something that really needs it.
Plus are you going to free the stack any time other than when you quit the app? I doubt it. The OS will free everything for you when you quit so there's no reason to waste time on that either.
The code so far looks like mostly a waste of time.
The new model at Microsoft is to run these big acquisitions as separate companies with a lot of autonomy. I suspect Github will do very well from here.
It feels more like a PR-grab "us-too" thing than a real moral stance.
I wonder if they would be doing this had it not been for the events of the past few weeks.
I expect more companies to follow suit. You can't have an impartial platform managed by partial people. Not saying they're wrong to do so, but it does contradict their music accessibility stance.
This precisely. What is going on in here? This story has nothing to do with Twitter banning certain accounts, so why is half the discussion about that?
Because much of politics is circular and virtue signaling is just as important to the libertarian-leaning HN population as it is to the 'snowflakes' that they loathe.
Why are we implementing a whole dynamically allocated stack for states before doing anything domain specific?
How many states could you possibly be expecting to have in a full game? 3? 12? 100? The examples of states were like the menu, action screen, and pause screen. So it sounds like very few. Drop the realloc'ing and free'ing and just statically allocate N states and be done with it. Save this complexity for something that really needs it.
Plus are you going to free the stack any time other than when you quit the app? I doubt it. The OS will free everything for you when you quit so there's no reason to waste time on that either.
The code so far looks like mostly a waste of time.