(Insert Your Encryption Key Here)

I'm not going to post The Number, but I'm going to talk about it.

What another big shouting match the interwebs have found themselves in. Is it wrong to post The Number on public sites? I don't think so. Anyone who can use it already has to write software that the regular Joe will grab. The Number is just a political/social status symbol now. Publishing is the The Number is the anti-crypto¹ parallel to the eye-liner high schooler shopping at Hot Topic. The point is making the point, more than what point exactly is being made.

So did the lawyers overreact? Of course they did, and consulting their clients before making moves on their behalf might be a decent idea. Maybe someone at the companies would actually realize the PR mess they might be stepping into. Maybe someone would say "Is the new technology stable enough to shake up our customers, yet?" Blu-Ray and HD-DVD are a techy's toy at this point, alongside wealthy status symbol usage. So, the large portion of the consumers who even use the technology are precisely those who know of and care about this story. When your ratio of Geek to Joe is that high on the Geek side, you need to act a little differently. Joe didn't even notice.

We sure noticed. Some of us noticed too much. I wish Joe noticed more.

Does anyone else mentally picture the AACSLA as Gollum and the The Number has their precious?

Comments

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

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...

Using a React Context as a Dispatch Replacement

React Contexts are the pretty little bows of the React world. Here's a really quick example of the kind of messy code you can cleanup by using contexts, without dragging in a larger dependency like Redux or even Flux. Starting backwards with a diff showing lines of code I was able to remove: All the properties I was able to remove were just pass-through. The Carousel component didn't care about any of them, but it had to pass through these callbacks so the multiple TaskList components inside the carousel could invoke actions. They were removed from the Component class itself, too, since it no longer needed to pass them through. Where did they all go? My ActionContext removed all the need for these passthroughs by providing a single simple helper method, action(), that components rendered under it can access. I really enjoy the pattern of passing a single callback through a context and removing what used to be lots of callback properties. Of course, I cou...

Developing Upwards

Search This Blog