Skip to main content

Movie Theaters, the End is Nigh! 1917 and Netflix

Movie Image from 1917
Courtesy of Dreamworks Pictures

Thoughts on Netflix and its Impact on Movie Exhibition After Seeing 1917

First the review (with no plot spoilers beyond what's in the trailer)

As a film, 1917 is excellent. The story is exciting, plausible, and well-told. The leads are likable and underplay their roles effectively. (These are British soldiers, after all.)  Some of the action scenes are stunning – the plane crash teased in the trailer is a high point. Another sequence in a bombed city was flashy (in both senses of the word), but I don’t understand what was lighting up the town he ran through at night. (Bombs? Flares? Who was firing them? Why?) The famous actors play their bits well, particularly Colin Firth, but I’m glad that the two leads are not well-known as it helps with the “it could be anyone” idea of a soldier grabbed at random on whom so much depends. 

More relevant to this post is that 1917 is a BIG SCREEN MOVIE. On the big screen the movie’s visually immersive, something that works particularly well in parts of the film that have us running through the trenches with the characters. My showing was a large-screen theater with Atmos sound, so you feel the explosions, yet the quiet lines were clearly heard. (I dread trying to understand the whispered dialogue on a home TV. I’d probably turn on subtitles – despite their ruinous effect on the experience – because home audio has been dumbed down over time. I miss stereo receivers!) One aspect getting well-deserved credit is the use of tracking shots, in which the camera moves along with the characters – especially a few shots where it skims across the water over a river or through a waterlogged bomb crater. These contribute to the “You Are There” effect that only the immersive theater presentation provides. 

Here’s my main point 

Go see 1917 on the big screen and savor these big screen experiences while you can get them, because your chances to do this will continue to diminish! 

I’m cynical about this because over the last few months, I’ve witnessed the bankruptcy of the Art Theater Foundation and the shutdown of the Art Theater – for now at least. The closing of the Art is an inevitable result of the seismic shift going on in movie distribution which I boil down to one word: “Netflix”.   Netflix (and its ilk, it’s not just Netflix, but they’re the “Kleenex” of this bunch) has crushed Art House movie distribution in three ways. 

  1. People have more content to watch, and our busy lives have ever-less time to consume content. 
  2. Netflix is cheaper than movies, and then once you pay you have a sunk cost effect that keeps you home and watching. 
  3. Netflix is purchasing content that would have been distributed to theaters (e.g. “Marriage Story”), which isn’t available for showing. (Except to make them eligible for Academy Awards.) Similarly, older content is pulled from exhibition to give more appeal to the streaming services. 

I expect more movie theaters to close in the coming years. This feels like another wave of closure similar to the impact of video tapes, DVDs, and HBO in the 80s and 90s. (Or the one in the 1960s from the growth of TV.) Then, as now, the competition for people’s entertainment time among more providers led to a reduction in movie theaters. 

Of course, movie theaters won’t go away completely. I think there’s always going to be a limited market for movie exhibition (and I hope to return to it one day!), but the last 3 years have seen a tremendous shift in movie-going habits. Movie theaters will continue to close and the movie-going experience will become a less-frequent event for a dwindling and aging audience, until it seems as quaint and deliberate as reading the Sunday paper or going to the shopping mall. 

One silver lining...

Also ending is the general rule that stories told should be 2 hours long. Because people are now used to consuming stories in one-hour chunks, movie-makers can tell an arc that takes 5, 15, or 50 hours.  People will be able to watch those in bits or binges, as they wish. I think that opens whole new exciting opportunities, but it will only hasten the end of movie theaters as it’s logistically impossible to replicate the bits/binges convenience that you can get at home or on your mobile device. (By the way, Martin Scorsese is not happy about that, but he should have thought about that ahead of time.) 

So, my advice is to see 1917 on the big screen, and appreciate it for the theatrical event that it is, and the end of the era that it represents.

Popular posts from this blog

The Tectonic Speed of Government, Part 1: Procurement

This post is my reaction to conversations about how hard it is to create change in government, and how government projects (and IT projects in particular) take so long from genesis to completion. This is part 1, about procurement; part 2 will address project implementations . PS - there was a surprise Part 3 of this series later! Warning : what follows is an “inside baseball” discussion of government IT procurement. I’m not trying to dissuade you from reading it, but if you’re not enmeshed in this world you might want to consider reading my articles on lighter topics like organizing your electronic life , the greatness of Abbey Road , or the story behind The Room . If you ARE enmeshed in this topic, then please don’t overlook my call to action at the end! Changing the process will take a group effort, and I’m hoping to get feedback on my scheme to create a library of reusable software specifications. By the way, this post’s first title was “The Glacial Speed of Government” bu

How To Videos: Lucity Queries with Microsoft SQL Server and Excel

What follows is not a blog, but some suggestions on using Microsoft SQL Server "Views" to query your Lucity data using Excel.   This information is intended to assist Lucity software users, and not for any nefarious purposes. I recommend watching the videos in Full Screen view and with HD resolution.  They're not as blurry as they look on this page!!  Each of these about two minutes long, but the original actions only took 50 seconds each.  (After recording them, I decided to slow them down to make them more watchable.) 1. How to create a SQL Server "View".   The video shows how to create a new View from the core Work Order table.  (WKORDER - see the data dictionary here .)  The video first shows the simple method of creating a view with all fields, then shows the more effective method of including only needed fields, and re-labeling them with their on-screen names. Music: "A View to a Kill" - Duran Duran 2. How to Connect to the Vi

Why the Tectonic Speed of Government?

The original name ("Glacial Speed of Government”) is both cliché and inaccurate, as it implies a faster pace than it used to. I decided that “Tectonic Speed” is more accurate because change in government shows tremendous resistance and moves slowly, but when it happens progress can occur in significant outbursts - and in those moments, there is great opportunity!     Click on "Read the Whole Thing" to access these links: Part 1 |  Part 2   |  Part 3  | Part 4 | Wait there's a Video?!  

The Tectonic Speed of Government, Part 3: It’s Never Over

Recently, I wrote two posts discussing why IT Projects take a long time: one on the Procurement Process and one about Project Implementations .  They were written during a time of three simultaneous projects, and they were therapy for me to exorcise some complaints... and make suggestions for others. From the start, I planned those as two topics – and I thought they'd finish the series. But this third part was a surprise, and the greatest lesson I learned from those projects. ********************************************************************************************* Disclaimer: All of the ideas expressed in this article are my personal statements and opinions, and do not reflect the opinions/statements of the City of Urbana. ********************************************************************************************* “It ain’t over till it’s over” - Yogi Berra on baseball, not IT projects. Trick Question : When is a software project over? Answer : Never

Tectonic Speed of Government, Part 2: Why do Government IT Projects Take So Long?

This is part two of my series on why government IT projects take so long. Part one complained that the Purchasing process is tough to navigate because methodically describing what you want to buy - and documenting your decision making - takes effort. That blog helped me vent some frustrations about parts of my job, although I admit that it was a little dry. (But please, this is Government Procurement.) With part two I’m on my home turf: the process that starts with the purchase of an IT tool and ends with its everyday use by people. If the process was successful, users are doing their jobs better than they did before. (A less successful outcome that also occurs: it’s harder to do their jobs, but at least their managers have better data.) This process, which I’ll refer to as the “Implementation” or “Project,” can take months or years for any organization - let alone a government. My first section explains why government IT projects take a long time, while the other three suggest