ursus_bonum

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.

This is clearly explained at the beginning of the article.

Google would have stepped on Octocat's neck and blown its pretty little head off.

Microsoft will either low-key torture it to death or leave it alone. Who's to say?

I use git in this particular way, and if you do anything different you are WRONG AND BAD or you have IMPURE MOTIVES!

I think I'll just hold my breath until the next Apple embarrassment.

Hmm yeah. Maybe censorship isn't the best weapon to use against Nazis.

This just in: "P" ruled totally illogical for "paste" "V" remains totally logical though of course

This satire is a little too subtle for me, assuming this isn't real.

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?

That's odd. gc shouldn't be collecting anything less than 2 weeks old by default.

That's fine but the article doesn't mention any popups. It just makes it sound like all of this will happen in the background without bothering the user.

This is such a classic example of not thinking things through.

The graphical manipulation stuff sounds cool until you think about what happens when it causes merge conflicts. I mean the graph stuff is still cool but it does very little for the hard problems.

The automatic committing for WIP and "magic" pushing/fetching sounds cool until someone switches branches and accidentally commits 3.1TB of junk files they left lying around and it automatically syncs to EVERYONE else on the project.

People complain now that Git is "too complex" just wait until it's automagically doing shit like that.

This. By the time you get good enough at Git to make a reasonable GUI, you don't need/want it anymore.

Me too. vim -u NONE is a life saver.

/me waits for someone to say we shouldn't have 3GB xml files in the first place, like I don't know that already.