ursus_bonum | 6 years ago | on: Writing a game engine in pure C: The Graphic Initialization
ursus_bonum's comments
ursus_bonum | 7 years ago | on: Microsoft Bing not only shows child pornography, it suggests it
This is clearly explained at the beginning of the article.
ursus_bonum | 7 years ago | on: Google was in the running to acquire GitHub, according to head of its cloud arm
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?
ursus_bonum | 8 years ago | on: The Eve programming language project is winding down
FlappyEve inspired my first "Tiny C Game", Flappy, now part of http://TinyC.games
ursus_bonum | 8 years ago | on: Oh shit, git: Getting myself out of bad situations
I use git in this particular way, and if you do anything different you are WRONG AND BAD or you have IMPURE MOTIVES!
ursus_bonum | 8 years ago | on: If your iOS 11 device unexpectedly restarts repeatedly on or after December 2
I think I'll just hold my breath until the next Apple embarrassment.
ursus_bonum | 8 years ago | on: Spotify is now deciding what music is politically acceptable for listening
Hmm yeah. Maybe censorship isn't the best weapon to use against Nazis.
ursus_bonum | 8 years ago | on: History of Emacs and vi Keys (2010)
This just in:
"P" ruled totally illogical for "paste"
"V" remains totally logical though of course
ursus_bonum | 9 years ago | on: Emacs is sexy
This satire is a little too subtle for me, assuming this isn't real.
ursus_bonum | 9 years ago | on: Twitter refuses US order to disclose owner of anti-Trump account
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?
ursus_bonum | 9 years ago | on: Reinventing the Git Interface (2014)
That's odd. gc shouldn't be collecting anything less than 2 weeks old by default.
ursus_bonum | 9 years ago | on: Reinventing the Git Interface (2014)
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.
ursus_bonum | 9 years ago | on: Reinventing the Git Interface (2014)
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.
ursus_bonum | 9 years ago | on: Reinventing the Git Interface (2014)
This. By the time you get good enough at Git to make a reasonable GUI, you don't need/want it anymore.
ursus_bonum | 9 years ago | on: Text Editor Performance Comparison
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.
ursus_bonum | 9 years ago | on: Snakisms
Indeed.
ursus_bonum | 9 years ago | on: The Legend of Zelda: Breath of the Wild Review
That game would have only been improved had down-thrust been available from the beginning.
ursus_bonum | 9 years ago | on: Bruce Schneier: 'The Internet Era of Fun and Games Is Over'
Or you're using Chrome.
ursus_bonum | 9 years ago | on: Classic IT short jokes collection
Two strings walk into a bar.
The first string says, "I'll have a rum and coke."
The second string says, "Same here.#uu6€^My¥ZZ~~0◀<bell><bell><bell><tab>000x[,_5"
And the first says, "Sorry, my friend here's not null terminated."
ursus_bonum | 9 years ago | on: How to Get Fired Using Switch Statements and Statement Expressions
Maybe compilers shouldn't have stupid extensions that make it possible to crash/hang the compiler?
page 1
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.