https://web.archive.org/web/20210108174645/https://www.adobe...
Bytes 2-3
An arbitrary but carefully chosen number (42) that further identifies the file as a TIFF file(Very few visitors to a Wikipedia page read its talk page, very few of them will further look at the archives of the talk page, let alone read every single comment and its corresponding commenter's name, and in this case as soon as the author knew the spelling to look for, the rest was straightforward for them.)
We are humans, everybody can miss things, I mentioned "hindsight is 20/20" but still, it was in the Wikipedia discussion page for the TIFF article all the time. It's a matter of fact and some random HNer found it in minutes/hours.
I repeat myself, it was probably better that he didn't found that out and went to write a hand-written letter to the alleged author's home address, it created a much deeper human bond, which is especially meaningful since Stephen Carlsen passed away not much later.
"The answer to this is very simple. It was a joke. It had to be a number, an ordinary, smallish number, and I chose that one. Binary representations, base thirteen, Tibetan monks are all complete nonsense. I sat at my desk, stared into the garden and thought '42 will do' I typed it out. End of story." from the man himself[1]
...but let us not ruin a good story with the truth. Remember why earth was built. The "real" answer might then be flowing in the ether.
[1] https://en.wikipedia.org/wiki/Phrases_from_The_Hitchhiker%27...
Edit: from the other comment, it appears it was in fact random...
https://en.wikipedia.org/wiki/Wikipedia:Verifiability#Self-p...
[1]https://www.mountainviewtacoma.com/obituaries/stephen-carlse...
This story is touching.
And thanks for being the historian of our culture-that-eschews culture (or so it seems to me sometimes, that tech tries to exist in a perennial present without acknowledging it's roots and history)
https://en.wikipedia.org/wiki/User:Scarlsen
Turns out the answer was on Wikipedia already :).
- one of them clarifies the (non-)involvement of Microsoft: https://en.wikipedia.org/w/index.php?title=TIFF&diff=prev&ol...
- and the other is even more interesting: though he is being scrupulous and removing a sentence that has no published citations, in his edit summary he confirms that it is basically true:
> The author of the original TIFF specification wanted TIFF to stand for "The Image File Format", but he was overruled by Aldus' president Paul Brainerd on the grounds that it sounded presumptuous.
(The edit summary says: Removed the "The Image File Format" sentence, since it only has eye-witness support (me, for one), but no published citatations)
> Primary sources that have been reputably published may be used in Wikipedia, but only with care
and I imagine a Wikipedia edit summary does not count as a reliable source. (For one thing, despite it being very plausible that the Wikipedia user Scarlsen who signed himself as Stephen E Carlsen is indeed that person—I believe it completely!—it cannot be guaranteed that it wasn't an impostor, for example.)
https://en.wikipedia.org/wiki/Wikipedia:No_original_research
Of course, if he was still alive he could have written a blog post or something like that and use that as a source, much like how it's likely this blog post will be used as a source for things surrounding the format and person.
>Yes it is true: the second word of a TIFF file, 42, was indeed taken from the answer to the Ultimate Question of Life, the Universe, and Everything, from Hitchhikers_guide_to_the_galaxy. StephenECarlsen 23:38, 12 October 2007 (UTC)
Well documented spec, easy to bolt on extras either as public tags - GeoTIFFs added projection metadata - or private, for your own needs.
Back in the day, to improve a desktop application's performance I found it was simple to create a custom reader and writer to handle cases where tiles were completely one single colour removing the need to decompress at run time.
Thank you TIFf!
edit: forgot about byte order...
I quite like the format, the only thing I would change is to have the option not to store directory information in a linked list spread throughout the file but in a simple array. Duplicate it at the beginning and end of the file and you've got resilience too (important in the age of floppies)
I’ve been using both TIFF and DNG this very week in my work (https://filmlabapp.com), so I was happy to read this post and learn about Steve Carlsen aka Mr. TIFF, whose work we’re still building on 39 years later.
I wrote a program processing GeoTIFF data. When I had started this project I chose GeoTIFF mostly b/c i wanted something simple. And I could load them in to Java's BufferImage class and manipulate them that way. But it seems all the pros exclusively use NetCDF and GeoTiffs are for noobs (working with atmospheric science data here)
GeoTIFF does extend "images" to cover more usecases, but a lot of stuff doesn't fit (like say a wind vector) and then you need some other container or metadata b/c you generally have many images. So I get the sense the complexity just ends up being moved elsewhere.
For forecast and climatological data I find NetCDF is vastly superior, but also much more complicated to work with due to the capabilities and how open the format is. Just have a look at the complexity of the CF Conventions to see what I mean: https://cfconventions.org/cf-conventions/release/v1.12.0/cf-...
For visualizing orthophotos and the like, I would choose GeoTIFF any day of the week, as they're easy to visualize across platforms using existing libraries. Using COGs you also get the functionality of a spatial index within each GeoTIFF file, meaning that you can stream subsets of GeoTIFF files without having to scan through the entire file for each request.
Seemed easier to let users preprocess their NetCDFs into GeoTIFFs manually. I have a bunch of hacky scripts to massage NetCDFs from different sources in to compatible GeoTIFFs
> meaning that you can stream subsets of GeoTIFF files without having to scan through the entire file for each request.
Interesting. My performance bottleneck right now is the user selects a small regions and then the program has to read in GBs of global precipitation maps (from IMERG) and cut out tiny squares. In the extreme cases it can mean ~2 minutes of waiting for a result. This means the user can't casually select and try out different regions with quick feedback. If you have a beefy machine you can keep it all in RAM sometimes and it works better.. but it's not ideal (my 16GB machine can only handle simpler scenarios)
I'll take a closer look at in the future. At the moment I just use Java's default TIFF reader and ImageBuffer class. Maybe it'd be easy to convert to COG format and adapt in a COG reader
Almost any digital camera RAW format is TIFF inside. And you can see how much kludges good metadata library needs to read all of them: offsets from the IFD, offsets from beginning of file with or without header, offsets from fields in IFD, etc, etc, etc. You take TIFF, you change header to make your format, and then you cannot implement this TIFF properly!
Even DNG (which is tiff inside) is mangled by camera firmware authors!
[…]
“Time flies like the wind.
Fruit flies like bananas.”
“What’s the answer to Life, the Universe, and Everything? 42.”Not today. I will try to remember the name of Mr. Stephen Carlsen as the inventor of TIFF format as long as I can. As a mediocre programmer, it is the least amount of respect I can pay for an unsung but talented engineer of an era that is fast going past us.
The article is great but the web site is supposedly related to a book "inventing the future".. which is nowhere to be found. Other than a big, slowly loading graphic, 3 posts and indexes for the book... the site doesn't provide a clue about where to acquire the actual (PDF only?) book.
I assume you have to sign up to find out more ?
On the web I can only find articles about the book.
So.. what is the deal in making the actual book hard to find ?
Edit: I think I cracked the code: Click Home, Open "Close Your Rings" article, scroll all the way down, find link: https://books.by/john-buck?ref=inventingthefuture.ghost.io
This page [0] still links to (when clicking the main image) an oddish seeming corner of your site that mentions purchasing the book but has no link to it
Based on the quality of the article, the subject matter of the book being right in the center of my wheelhouse and the references I could find on the internet, I just ordered a copy (apparently a paper copy), look forward reading it.
https://en.wikibooks.org/wiki/PSP/Homebrew_History?useskin=v...
It took eight years, and was a lot of work. The process that he mentioned is quite familiar. Many of the folks we interviewed have since passed away. Some, before the book was complete.
I had downloaded the final Aldus TIFF specifications document, hoping to find the author’s name. However, the name is seemingly written in white text on white paper - making it invisible. What?
[1] SHA256: dbcdf729182937ecff415dfd06806894bf03bfd741291aa3ad7ba45335673def, modify date 2002-05-10, created by Acrobat Distiller 4.05 for Windows, e.g. https://www.itu.int/itudoc/itu-t/com16/tiff-fx/docs/tiff6.pd...
[2] SHA256: 8cb1e1a2226e423ba8b88f57366a30ef1b7ad6109443ebdda072b952739a8d76, modify date 1995-09-14, created by Acrobat Distiller 2.1 for Power Macintosh, e.g. https://download.osgeo.org/libtiff/doc/TIFF6.pdf
Not mentioned in either the article or the tail end wikipedia article iamge was the early adoption of TIFF by the mapping and geodetic community to store raster line data (maps, images, and raw sat and instrument platform multichannel line data).
The tagging format made the embedding of spheroids, datums, projections, origins, lens and focal specifications relatively easy (plus or minus the usual Tower of Babel Tag Naming and Meaning Confusion).
What a journey and congratulations to SC (don't want to spoil it) on your 15 minutes and rightful restoration as inventor of TIFF, take your place in history.
It's weird to see times one has lived through presented as ancient history....
I just remembered Orkut. Though I suspect Google has backups or Orkut and Google+ somewhere. I wonder if Yahoo Answers is still on a tape somewhere?
I now adopted the practice of recovering the texts I deem worthy from way back machine and downloading all yt videos I really like locally.
But ofc one day I’ll also hit the bucket; still have to work out a contingency plan for my archive for that …
I think the reason TIFF was so prevalent was it already had support for CMYK color space (even though many books were printed in black and white) and for lossless compression (as TFA mentions).
It was a "one size fits all" format and so our 100 or 250 MB (!) Zip drives [3] exchanged between authors/publisher/typesetters often contained TIFF files.
> For as long as I have published my books, one of my overarching goals was to give credit to those who actually invented the hardware and software that we use.
So thank you Mr. Stephen "TIFF" Carlsen!
[1] https://en.wikipedia.org/wiki/QuarkXPress
I hate to nit-pick on such a beautiful story but that it ended with a faux-Ghibli profile picture is just sad.
How can someone working so hard to humanize technology and preserve history, justify this soul-less commodification of art? Do the animators deserve to get treated as anonymous model trainers without their consent, names and frames lost in a dead ocean of bit-vectors?
Thank you for all the efforts that went into preserving the memories of those that built the world around us.