<?xml version="1.0" encoding="utf-8"?><rss version="0.92">
<channel>
	<title>Paul Kuliniewicz</title>
	<link>http://www.kuliniewicz.org/blog</link>
	<description>After all, it could only cost you your life, and you got that for free.</description>
	<lastBuildDate>Wed, 18 Jan 2012 04:01:40 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	<!-- generator="WordPress/3.1.4" -->

	<item>
		<title>Going dark on Wednesday</title>
		<description><![CDATA[Like many far more important Internet sites, this blog will be going dark on Wednesday to protest the proposed Internet censorship bills SOPA and PIPA. If passed, these bills would give content owners the power, without judicial oversight, to shut down entire web sites and compel banks and other financial institutions to freeze the site [...]]]></description>
		<link>http://www.kuliniewicz.org/blog/archives/2012/01/17/going-dark-on-wednesday/</link>
			</item>
	<item>
		<title>Neutronium update &#8211; Dec 12, 2011</title>
		<description><![CDATA[I&#8217;ve continued working on Neutronium daily, but for the past week or so I&#8217;ve been focusing on refactoring some of the code I wrote earlier to facilitate actual new features. The biggest change has been putting most of the room-related logic in the STM monad, instead of having parts of it in STM and other [...]]]></description>
		<link>http://www.kuliniewicz.org/blog/archives/2011/12/12/neutronium-update-dec-12-2011/</link>
			</item>
	<item>
		<title>Reading is dangerous (if you&#8217;re writing Haskell)</title>
		<description><![CDATA[In Haskell, the read function is the usual, simple way to parse a String into a value of some other type: ghci&#62; :t read read :: Read a =&#62; String -> a read can parse anything that implements the aptly-named Read class. All the standard numeric types implement Read: ghci&#62; read &#34;42&#34; :: Int 42 [...]]]></description>
		<link>http://www.kuliniewicz.org/blog/archives/2011/12/07/reading-is-dangerous-if-youre-writing-haskell/</link>
			</item>
	<item>
		<title>Neutronium Demo Video</title>
		<description><![CDATA[With Renee&#8217;s help, I recorded a six-minute-or-so demo of Neutronium, the game I&#8217;ve been working on since the beginning of November. You&#8217;ll probably want to play it at 720p (HD) and full-screen in order to be able to read the text. Neutronium is a web-based game inspired by a game inspired by the light-cycle game [...]]]></description>
		<link>http://www.kuliniewicz.org/blog/archives/2011/12/02/neutronium-demo-video/</link>
			</item>
	<item>
		<title>Working on a video</title>
		<description><![CDATA[By popular request, I&#8217;m working out a way to record a quick video of my game in action. Before I do that, though, I want add an option to select the size of the game area. Right now it&#8217;s a hardcoded size, and it&#8217;s large enough to be awkward for an embeddable video. Something smaller [...]]]></description>
		<link>http://www.kuliniewicz.org/blog/archives/2011/12/01/working-on-a-video/</link>
			</item>
	<item>
		<title>LoCo Day 30</title>
		<description><![CDATA[Today I added support for command-line options when starting the web server. Specifically, it&#8217;s now possible to specify which port the server will listen on, and the hostname that will be used when showing type-safe URLs. Previously, both of these were hard-coded in such a way that made it difficult to use the server on [...]]]></description>
		<link>http://www.kuliniewicz.org/blog/archives/2011/11/30/loco-day-30/</link>
			</item>
	<item>
		<title>LoCo Day 29</title>
		<description><![CDATA[Two small but welcome changes today: First, I reduced a lot of the lag during game play by excising a bit of debugging code on the server. The server had been printing out to the console the session context for each request before processing it further. Since I had gotten sessions working quite some time [...]]]></description>
		<link>http://www.kuliniewicz.org/blog/archives/2011/11/29/loco-day-29/</link>
			</item>
	<item>
		<title>LoCo Day 28</title>
		<description><![CDATA[Today I tried to solve the problem of the &#8220;ready to play&#8221; button swallowing keyboard input when the game starts, even though the button was disabled. Apparently jQuery doesn&#8217;t let you put the input focus on the document itself, which is where the keyboard input handler is attached. I ultimately settled on hiding the button [...]]]></description>
		<link>http://www.kuliniewicz.org/blog/archives/2011/11/28/loco-day-28/</link>
			</item>
	<item>
		<title>LoCo Discontinuity</title>
		<description><![CDATA[Apparently my posts for Friday and Saturday never made it out of draft form, and so didn&#8217;t appear on the blog until now. Just in case you were wondering what I was up to after Thanksgiving.]]></description>
		<link>http://www.kuliniewicz.org/blog/archives/2011/11/28/loco-discontinuity/</link>
			</item>
	<item>
		<title>LoCo Day 27</title>
		<description><![CDATA[Success? The basic gameplay in the browser is working now, so for the first time ever it&#8217;s actually possible to play the game. My loving girlfriend Renee helped me test that it does indeed work with multiple players, and she even beat me in the first real match we played against each other. For posterity&#8217;s [...]]]></description>
		<link>http://www.kuliniewicz.org/blog/archives/2011/11/27/loco-day-27/</link>
			</item>
</channel>
</rss>

