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.
Labels:

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. :)
4:05 AM
Post a Comment

Popular posts from this blog

My Software Job Transition Strategies?

I’ve been spending a good deal of the last two days preparing mentally for starting a whole new challenge as a developer. New things aren’t new to me, but this is different and big enough really call for some Deep Thoughts ™. For one thing, I’ve made a big move from the world of Python web development to totally other Python work and while web development has never been the only thing I do, it has been the only work that paid the bills. That transition isn’t one that bothers me or daunts me, though. Instead, I’m thinking about transitioning to the scope of the work I’m getting into. For a long time, I juggled multiple clients and client projects every day, so no single project usually took up most of my time. Every developer juggles time through the day, but exactly how that works in each company and on each project varies a lot. I was looking for a place that I could really focus in a way that I haven’t for a long time. I think I found that, but now I have to deal with the consequen...
Post a Comment
Read more

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 operat...
1 comment
Read more

The Snake Pit is About to Burst

The signs are all over the place. I can count at least five implementations of Python today: CPython, CL-Python, Jython, IronPython, and PyPy. The use of the language is sky rocketting and set to grab real mind-share as the hype over Ruby subsides. Things are looking good for a favorite green snake and british comedy troop reference, aren't they? Trouble is on the horizon in the very ingredients that could push us into true success. Our community and our very language is in danger of segregation, unless we all do something about it and learn to get along. One of the most visible dangers (to me) is being ignored for various political, cultural, and non-technical reasons. IronPython's users are increasingly pushing IronPython-only recipes, libraries, and tutorials. No one is talking about the transition of the alternative implemenations to CPython 3.0 compatability. To make matters worse, we still can not define the language without refering to an implementation. This is very un...
11 comments
Read more