Skip to main content

Less for More in Media

I think this is appropriate, because my favorite software is a transport for media. YouTube, music downloads, blogs, and web comics are all old media turned new. TV and movies are old and web videos are new. CDs are old and downloads are new. Books and magazines are old and blogging is new. Newspaper comics are old and web comics are new. Why did I single out comics? Because, Scott Adams, of Dilbert fame (who has an excellent, non-comic-centric blog) took fledgely comic cartoonist, Scott Meyer, under his wing. This is old teaching new, and is interesting to watch.

On the first post from Adams, I commented about how many cartoonists might not even want the traditional route of syndication, and will choose to stay with web formats. On part 2, I commented as follows:

It is becoming one of the defining characteristics of the New Media that more people can make less money. To the eyes of the Old Media, this is obviously a Bad Thing. No one gets quite as much attention or makes quite as much money, but if you look at how many more people can make it at least to a good level, and you sum it all up, I'd be sure the overall industry makes more. To add to that, huge chunks of the money aren't going to syndication agencies and other central entities. More of the less money stays with the artists. The same is happening in moves from newspaper comics to web comics, music from CD to download, and sixty dollar video games being pushed aside for dozens of ten to twenty dollar smaller titles, each. The end is more variety, and a better chance of finding something that you like, more people make a living on what they love, and more of the profits staying with the people who are actually doing the creating. The old media will not go away for a long time, and we still need it, but the model simply changes. Cartoonists aren't supposed to make a million dollars a year any more, and that's OK if, instead, twenty or more cartoonists can make a very decent living with their craft, don't you agree?

Comments

Popular posts from this blog

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…

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 only re…

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…