Archive
2014
May
2013
January
February
March
April
May
June
July
September
November
December
2012
February
March
April
May
June
July
August
September
October
November
December
2011
January
February
March
April
May
June
July
August
October
2010
September
October
November
December
Jun. 04, 2013

The Luddite: Dot Matrix Printers

by Ira Flatow

Click to enlarge images
Having recently travelled through too many airports and suffered the depressing indignity of air travel these days (don't get me started), I had plenty of downtime whiling the hours away at airport gates to find an answer to a question about airports that's been bothering me for quite some time: Why do the airlines still use those old fashioned dot matrix printers at the gates? The ones where tiny pins smack a ribbon and create letters and numbers in a matrix form. Popular circa 1983. 
 
Here's what I mean. If you look behind any airport counter, you'll see these printers—maybe even an old Epson 80—clacking away and spewing out reams of ancient dot matrix paper. Some of it comes off as a long roll, like giant toilet tissue. The more expensive kind, the long continuous ribbon of paper, fan-folds itself up as it streams out of the printer. We of a certain age have all been there, done that, and have moved on to the laser printer and then the inkjet.
 
But why are the airlines luddites here? Why do they continue to use these old clackers? Why have they not moved to laser or ink jet? What do they know, that I don't?
 
Pointing to a clipboard holding a jumble of the old paper, I asked an airliine flight attendant why the romance with the old style. He smiled, looked around a bit, and in a motion best described as rubbing his thumb agains his forefinger, he silently mouthed the word "money." Too cheap, he said, to upgrade. 
 
I'm not one to argue with an employee who knows the indside dirt more than I. But after observing how pilots and desk and flight attendants wrestle with the pulp, I've concluded that it may not be only about the money. Just watch how much paperwork is involved with each flight, and you'll agree these printers are the right tools for the right job.  
 
There's an advantage to having the paper emerge in a long sheet rather than individual pages. Each airport gate is really a desk, a tiny office, where the employees come and go. The amount of paperwork that prints out for each of those flights is mind boggling. And all that paper is handled by the pilots, the attendants, the gate folks, yada yada. Imagine if they were all single sheets. What a mess that could drop and fly away (pun sort of intended). Plus when you're in that last minute rush to board, it's much easier to fold up that roll of paper and stuff it willy-nilly into a clipboard. If you don't get it aligned perfectly, it ain't going anywhere. Worst that can happen is that one end droops down a bit. 
 
Am I right about this? Not sure. I'm not going to spend much time moving up the airline p.r. ladder seeking an answer. Maybe it's cost. Maybe it's not. This is how I look at it: Sometimes the old tech is still the best tech. 
About Ira Flatow

Ira is the host and executive producer of Science Friday.

The views expressed are those of the author and are not necessarily those of Science Friday.
EVAL ERROR: Entity: line 1: parser error : Space required after the Public Identifier

                                                 ^
Entity: line 1: parser error : SystemLiteral " or ' expected

                                                 ^
Entity: line 1: parser error : SYSTEM or PUBLIC, the URI is missing

                                                 ^

Code:
line 1: package tmpevalpackage;
line 2: sub doEval { 
line 3: 	my($parent);
line 4: 	
line 5: 	if($LayoutManager::url_resolved_values{'SEGMENT.nickname'}) {
line 6: 		$parent = $LayoutManager::url_resolved_values{'SEGMENT.nickname'};
line 7: 	}
line 8: 	elsif($LayoutManager::url_resolved_values{'VIDEO.nickname'}) {
line 9: 		$parent = $LayoutManager::url_resolved_values{'VIDEO.nickname'};
line 10: 	}
line 11: 	elsif($LayoutManager::url_resolved_values{'DOCUMENT.nickname'}) {
line 12: 		$parent = $LayoutManager::url_resolved_values{'DOCUMENT.nickname'}
line 13: 	}
line 14: 	
line 15: 	if($parent) {
line 16: 		my(@books) = &Database::SelectClause('BOOK',"parent = $parent");
line 17: 		if(!@books) {
line 18: 			$parent = '';
line 19: 		}
line 20: 	}
line 21: 	
line 22: 	if(!$parent) {
line 23: 		my(@sel) = &Database::SelectClause('GLOBAL','record all ""');
line 24: 		if(@sel) {
line 25: 			$parent = 'GLOBAL.' . $sel[0];
line 26: 		}
line 27: 			$main::ENV{'reading_header'} = "FEATURED READING";
line 28: 	}
line 29: 	
line 30: 	 = '';
line 31: 	
line 32: 	if($parent) {
line 33: 		my(@books) = &Database::SelectClause('BOOK',"parent = $parent");
line 34: 		0 = 0;
line 35: 		my $dots;
line 36: 		foreach(@books) {
line 37: 			my(%data);
line 38: 			&Database::GetRow($_,'BOOK',\%data);
line 39: 			my($status,$title,$author,$url,$image,$width,$height) = &SciFri::Schema::getAmazonItem($data{'isbn'});
line 40: 			if($data{'title'}) {
line 41: 				$title = $data{'title'};
line 42: 			}
line 43: 			if($data{'author'}) {
line 44: 				$author = $data{'author'};
line 45: 			}
line 46: 			if($status eq 'ok') {
line 47: 				 .= "<div class=\"box-2x1-item box-slide\" data-href=\"$url\">";
line 48: 				 .= "	<div class=\"box-2x1-item-photo\">";
line 49: 				 .= "		<div class=\"image-wrapper\" data-jsclass=\"imageWrapper\" data-align=\"right\">";
line 50: 				 .= "			<img src=\"$image\" data-width=\"$width\" data-height=\"$height\">";
line 51: 				 .= "		</div>";
line 52: 				 .= "	</div>";
line 53: 				 .= "	<h4>$title</h4>";
line 54: 				if($author) {
line 55: 					 .= "	<p>by $author</p>";
line 56: 				}
line 57: 				 .= "	<div class=\"box-2x1-more-button\"><a href=\"$url\"><img src=\"/images/v1/icon_text_more_white.png\" width=47 height=15 border=0></a></div>";
line 58: 				 .= "</div>";
line 59: 				++0;
line 60: 			}
line 61: 		}
line 62: 	}
line 63: 	if($parent eq "GLOBAL.1") { $main::ENV{'reading_header'} = "FEATURED READING"; }
line 64: 	else { $main::ENV{'reading_header'} = "RELATED READING"; }
line 65:  };
line 66: &doEval();
line 67: 1;

Science Friday® is produced by the Science Friday Initiative, a 501(c)(3) nonprofit organization.

Science Friday® and SciFri® are registered service marks of Science Friday, Inc. Site design by Pentagram; engineering by Mediapolis.

 

topics