a grinchy star wars christmas

“Star Wars: The Force Awakens” has by any measure you want to apply been an incredible financial success. As of today, 30 December, it’s crossed the $600M gross receipts mark, breaking yet another record time-wise in its unstoppable (it would appear) race to $1B and beyond. Everywhere you look, everyone is gushing over how Star Wars has boosted not only its own sales, but the overall North American box office gross receipts to $11B+ for the year.

If I’m lucky I hopefully won’t add to the growing pile of cash surrounding this Star Wars movie.

I have for decades taken a dismal view of the entire Hollywood Industrial Complex. I can’t remember how far back my dark view goes, but it was kicked into high gear with the passage of the Digital Millennium Copyright Act in 1998, which essentially made making copies, any copies, felonious behavior, by the “dissemination” of means and methods for breaking digital rights management, or DRM. It went so far to criminalize the mere act, even if no actual infringement (especially for profit) takes place. And that was used to lard up digital systems with hardware and software in our electronic devices to enforce it.

This incredibly invasive law and the incredibly abusive system that that has grown up to enforce it since then has motivated me to avoid just about everything the HIC can produce, from music to movies. The only thing I buy in any quantity anymore are dead-tree books, if for no other reason that they can’t be erased or recalled, unless the Firemen come to claim my books.

It further inflames my passions against the HIC when I read all the stories trumpeting 2015’s record ticket sales of just over $11B. And this isn’t the first year with such records. This year’s record breaks the last record set a mere two years ago in 2013 of $10.9B. So it’s not like a few record years in the midst of many poor years, like the US car industry for example. The HIC has been stepping from record to record each year, riding abusively and heavily on the backs of the US citizens, helped with the gross enforcement of the DMCA and other similar actions. When you see such a colluding, abusive marketplace, investigations usually take place and people get sued. But not the HIC. Instead, with their carefully bought legislative drones, they make billions, talking out of one side of their mouths about how wonderful it is, while at the same time talking out the other about how they’re being driven to the poor house by copyright abusers. The only real copyright abuse is with the HIC, who are masters at it. And so I do as little as possible, personally, to help put money into a system that abuses me in so many big and little ways. I don’t buy tickets, I don’t watch movies at the theaters if I can help it, and I don’t stream anymore (I streamed very little to start with), especially music.

I’ve a confession to make: when the first Star Wars movie was released in 1977 I saw it 24 times. That’s right, 24 times. That’s because the last good science fiction movie I saw with space ships was 1968’s “2001.” That period from 1968 to 1977 was a vast cinematic wasteland for me, so when the first Star Wars film was released I was incredibly motivated to see it as much as possible (it also helped that I was 23 at the time, a key age for such oddball behavior). I kept going back to tease out how the special effects were created (I was heavy into film still photography back then, and nursed the ambition of going into film making; we all know how that turned out). Key to supporting this behavior were ticket prices in 1977. I could afford it back then because tickets cost $2, dropping to $1, per showing. That is literally an order of magnitude less than today.

I’m not the only one not buying tickets. In spite of all the record breaking money made, the number of tickets sold has declined to levels not seen since 1996. That’s because the cost of tickets, driven by new gimmicks such as 3D and IMAX screens, has pushed single ticket sales well above $10 in just about every market across the country, especially for 2015’s Star Wars movie. Think about that for a moment. The number of tickets sold is at a level not seen since three years before the DMCA was passed. Number of tickets sold has been dropping steadily for years now, driven in part by a poor quality product as well as ever higher prices. Lest you think that this current Star Wars release is some artistic wonder, think again. There are many vocal critics who aren’t all that keen about the movie, such as this example at Forbes, and for many good reasons. The drive to see the movie is due in no small part to just how bad the last three movies were, not how good this one is. Remember that this movie was directed by JJ Abrams, the same auteur who gave us 2009’s Star Trek reboot.

While there are a few tongue-in-check movie reviews scattered around this blog, there are only a few. It seems like every time I break my vow of non-viewing I come away disappointed. I think I’ve finally learned my lesson; to avoid future disappointments and an appreciably lighter wallet, I’ll stay away. Not just from Star Wars, but all the other hyped science fiction films headed my way.

trying to build a better android application (part 1)

The circumference of Earth, in miles, which is the product of pi (3.1415926) times Earth’s diameter (7,918 miles).
Samsung Galaxy S4 running Android 5.0.2

Since sometime around 2011 I have dabbled with Android programming, starting with Android Honeycomb. My reasons for targeting Android 3.0 in were:

  1. Honeycomb was explicitly for tablets and I was very interested in the tablet form,
  2. Just about any device could become a developer target device without having to register with Google (unlike Apple),
  3. It had become “interesting” with its new additions in support of tablets,
  4. The Eclipse tooling seemed mature enough, and
  5. I had grandiose ambitions about writing the Next Great App.

That last point included the idle idea of making heaps of money, but that was quashed quickly and rather brutally by the harsh reality of the Android app marketplace.

That didn’t stop me from continuing to tinker with Android over the past few years. My hard drive is now littered with dozens and dozens of toy applications (toy in the sense that they were never launched into the marketplace). Then, one day quite recently, Google saw fit to update my two Nexus 7 2013 models with Android Lollipop 5.1 and 5.1.1 (and I have no idea why one is a point release higher than the other). I even have a Nexus 7 2012 with Lollipop 5.1.1, for all the good that older tablet can use it effectively. A Nexus 7 2012 with Android 5.1.1 is the very definition of molasses-in-January slow. A Nexus 7 2013 with Android 5.1/5.1.1 is at least usable.

Along the way to getting my Nexus 7s upgraded, AT&T upgraded my Samsung Galaxy S4 to their version of Lollipop 5.0.2. That’s what I’ll be using to test my app, rather than the larger Nexus 7 tablet. The S4’s size is about the same physical size as the HP32sII.

With the Nexus Lollipop updates came a built-in calculator app that I quickly came to loath. I don’t know who wrote it, but whomever it was has no concept of what a calculator truly is, especially regarding operational usability. Rather than merely complain about it I decided this was a golden opportunity to dig in and write my own, going by the old adage that if you think you can do better then do so.

Historical Background

I was an incoming electrical engineering freshman at Georgia Tech when the Ga Tech bookstore started to carry the Hewlett Packard HP-35 for $395. As a Georgia resident, that was about how much my tuition and books cost at the time. On my limited budget there was no way I could justify trading in my slide rule (yes, I had one of those) for the HP. But brother, I sure wanted one in the worst way.

The next spring after the HP-35 release I purchased the less expensive Texas Instruments SR-10 model 2 for $90. That lasted me for about two years until I upgraded to another wedge-shaped calculator, the SR-16. I loved those wedgies because they were built like bricks and took a lot of use and abuse. Two years after the SR-16 I advanced to the TI-58, followed rather quickly by the TI-59. After those TI models, when it came time to replace them due to heavy use, my calculator allegiance switched from TI to HP because TI had so cheapened their calculator construction in the interim. I still have working calculators from that period here at the house, but they’re an HP-16C (which I used for digital design work) and an HP-32sii (for general engineering). I have an old TI-95 Procalc I picked up at a heavy discount some point in the distant past. I bought it more for sentimental reasons at the time. It now sits in a drawer, totally unused.

The General Design

I decided to write my own calculator app, based on my experiences with both HP and TI. I did not set out to build an emulator of any particular model. What I wanted was something that fit the ethos of those calculators, especially the HP-67/HP-41C and TI-58/59 calculators. Those machines were their respective companies best of breed calculators. None before or since have quite measured up. It was one of my goals in writing my app to borrow from, but not slavishly re-create, their best ideas.

My app is based on the algebraic notation that TI also used, that is, typing in an arbitrary formula from left to right using parentheses for precedence control and ending the formula with the equals key. That’s why you’ll see those keys on my initial design. It’s a harder design as apposed to reverse Polish notation (RPN), the method used by HP. I won’t get pulled into the age-old argument as to which is better. I just decided for personal reasons to go with algebraic.

Preparatory

The application provided an opportunity to move up to writing idiomatic Lollipop applications using Google’s Material design rules. That meant moving from Eclipse to Android Studio. It also meant having to drop a lot of old coding practices. I’ve been using Android Studio since its beta releases, having created a series of (again) toy applications based on every type of starting template that Android Studio provides. For example my calculator was started with the Blank Activity template, an absolute minimal project, the Android equivalent to “Hello, World.”

I want to note that I will not be going through a step-by-step initial setup for this project. I will be talking about the issues of building this project, and what I’ve discovered along the way with using Android Studio v1.2 and Material Design, both good and bad, primarily good.

Current Functionality

The app can perform all four basic functions; add, subtract, multiple and divide. That means all the data entry keys (all numeric, decimal point), the change sign key, and the equals key work as expected. Clear (C) and clear entry (CE) keys work as expected. The Inverse (INV) and LNX (loge(x)) keys work. The keys that do not work are the Exponent Entry (EE) and the left and right parenthesis keys. You thus can’t perform full algebraic calculations nor can you enter a very large number in scientific notation, such as Avogadro’s number, 6.0221413 × 1023. I may implement that functionality while writing these posts, but that’s the current state of the app right now after several weeks of on-and-off work (mostly off).

What’s Next

The next entry in this series will begin with a general outline of the files in the application, how the app evolved from its initial creation until now, and the problems I encountered along the way with their solutions.