Skip to main content

How To Fullfil The (Geek) Rockstar Dream

I've been putting a lot of though to my ongoing desire to write something in the way of a video game. This was my original foray into programming and I just didn't stick with it. Turns out I am such a geek that I actually found database design and protocols more interesting than first-person shooters. Go figure. Still, the old dream burns inside me. I've spoken with a few people here and there that could gain interest if I started something, and I'm thinking the time is arriving that I buckle down into the nights and see what I can do.

I've been looking pygame versus pyglet and hoping to find a ready-to-use accelerated sprite library. Although I really want to write a straight Python, installable game, the lure of the web is strong. There are a lot of fun ideas I could try there, and probably a much larger audience I would reach. Of course, there are pros and cons to both.

















Web-Based
Installable
Pros
  • Zero installation
  • Higher number of users
  • One target platform (for the server software)
  • More powerful result
  • Allow mods easier
  • More justified to charge for the game
Cons
  • Nearly impossible to charge players
  • Limited capabilities
  • Disperse browser platforms
  • Less people will play the game
  • More capabilities to waste my time on
  • Disperse target platforms


My options really aren't very clear. I don't know which I'll go with. Either way, I'm sure I'll bring Python into the mix on some level. Of course, I don't necessarily have to choose one or the other. I'm considering the option of taking both routes. The development time would take longer, but I could try an interesting approach of a demo or slim version of the game for free use, probably supported with advertising. Anyone who enjoys the game enough can buy a full version for download.

There are even techniques to share a significant amount of the development effort between the two versions. I'm sure that would give me some interesting things to blog about and perhaps some fun pieces of code to share.

Of course, all of these options don't even get into the questions of platform support, or javascript versus Flash for the web development. The different choices are really a bit much.

Comments

Anonymous said…
A similar thing happened to me. I was taking a Games Development class last semester, and somehow became more interested in learning about open source, and it's pretty much been downhill from there. :)

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

The Range of Content on Planet Python

I've gotten a number of requests lately to contribute only Python related material to the Planet Python feeds and to be honest these requests have both surprised and insulted me, but they've continued. I am pretty sure they've come from a very small number of people, but they have become consistent. This is probably because of my current habit of writing about NaNoWriMo every day and those who aren't interested not looking forward to having the rest of the month reading about my novel. Planet Python will be getting a feed of only relevant posts in the future, but I'm going to be honest: I am kind of upset about it. I don't care if anyone thinks it is unreasonable of me to be upset about it, because the truth is Planet Python means something to me. It was probably the first thing I did that I considered "being part of the community" when I submitted my meager RSS feed to be added some seven years ago. My blog and my name on the list of authors at Plan

Javascript Module Loaders Considered Harmful

Introduction I’m coming to an opinion of Javascript module loaders that is profoundly negative and I’d like to express why I think they are, generally, a bad idea. However, I do think they have a place, which I’ll get to at the end. Now, I understand I might be in the minority here. Between the competing specifications of CommonJS and AMD modules, loader systems like RequireJS or the (honestly really awesome) Google Module Server, and the huge cultural influence of Node on the Javascript world, you’d be hard pressed to argue against Javascript modules these days. Scripts are old hat, too stupid, too inflexible. Everyone knows that and no one would make an argument in their favor, right? I’m going to step out on a limb and say “Javascript Module Loaders Considered Harmful” and I know the baggage involved with declaring something “Considered Harmful”. I mean every ounce of context that phrase carries with it, and I hope I can persuade you. Harm #1: Confused Debuggers