jarrodwhaley.com

I make films. I'm also a nerd.

Archive for 2012:

Here’s An Idea:

A Chrome extension which lets you read:

OR:

  • view anything at all on the most incompetently built Web site ever, Dumbshit Central;

…and then sets your computer on fire, just after displaying a pop-up message which reads:

KILL YOURSELF. QUICKLY.

Samsung Is Hilarious

Allow me to belatedly (and perhaps superfluously) make a quick comment on this whole Apple vs. Samsung rigamarole: Ha ha ha, hahahahaha. Ha. Ha! Ha.

But on a serious note: How can anyone find it acceptable that Apple spent five years pouring brainpower and money into inventing a thing that every single human wants, and Samsung said, “yeah, that looks like it’ll kill our phone business, let’s shit out a cheap copy ASAP and then act all righteous about having shat a sub-par simulacrum.” Come off it. Which do you turds hate more: Apple, reason, or quality gadgetry?

OS X System Service – Converts Markdown Files To HTML Files

I needed a way to batch-convert a bunch of Markdown files to corresponding HTML files, so I wrote this simple OS X system service which does just that. I thought it might be helpful to others, so here you go. Happy nerding.

Note: This service presupposes that you have Fletcher Penney’s Multimarkdown installed in usr/local/bin. Edit the path in Automator if necessary.

Download:

FoldingText Is Badass

I admit when I first heard about FoldingText (via Brett Terpstra, I believe), I had no idea why it might be something I’d want to use. On the surface it’s a Markdown editor with foldable headers, but underneath it’s a lot more than that. You can easily drop to-do lists and timers into your document using plain-text only–in other words, you type “todo.timer” on one line, hit return, type “write for 15 minutes,” and bingo, you have a timer.

It’s still in beta, but I recommend it anyway. It’s probably the best, most efficient productivity app I’ve ever tried. If you use a Mac and find it useful to organize your work, go grab FoldingText.

Review: BERNIE

Richard Linklater | 2011

Well enough done, but the weird mixture of tones in the staged “interview” segments rubbed me very much the wrong way. There are real Texans doing real interviews mixed in with real Texans reading fake lines mixed with Matthew McConaughey doing his “Danny Buck” shtick. The lack of tonal consistency demonstrates–better than any argument I might make–the needlessness of the insipid “there are interviews!” approach itself.

It’s a mess both rhetorically and formally, but in gross effect it achieves a passingly sensitive treatment of the issue of social interplay among socially unequal players. By the time the dirty deed is done, Bernie’s humanity is adequately established. Perhaps the “evil” (to quote an “interviewee”) of Maclaine’s character might be more clearly demonstrated–we get about five minutes of shitty behavior, and otherwise she’s a sweet, giving lady. Maybe it could be argued that a cartoonish evil would lessen the complexity of Bernie’s break with strict morality, but I argue the opposite: he’s too candy-coated, and she’s not shit-coated enough for me to believe a sweet man might snap.

In the end, it just barely manges to do what it needs to do. That ought not be enough to give it even a tepid thumbs up, but in the context of today’s cinematic landscape this is probably / almost / sort of / as good as it gets.

Should I?

It’s an argument I’ve had with myself time and time again: is it seemly for a filmmaker to write reviews of films? I’ve never found a satisfactory answer. At this moment, I generally tend to lean toward the idea that anything I have to say about anything at all is best expressed in a film. And yet I’m about to post a (brief) review of a film anyway.

I may post more reviews. I may stop after this one. I may soon delete this post and the next one. I don’t know. I’m not even sure why I’m writing this. Maybe it’s just so you’ll know that I think about things before I spray them onto the Internet. And so…

You Have To Love Linux

Imagine an error message like this one in the context of any other operating system. It’s folksy, overtly helpful, exquisitely verbose…this is what happens when real people write error messages, without being filtered through committees and Corporate Bullshit Machines.

WARNING your program is becoming multi-threaded, but you are using an ObjectiveC runtime library which does not have a thread-safe implementation of the +initialize method. This means that any classes not already used may be incorrectly initialised, potentially causing strange behaviors and crashes.
To put this into context, the runtime bug has been knoown for several years and only rarely causes problems … the easy workaround being to ensure that any classes used by a new thread have already been used in the main thread before the new thread starts.
If you are worried, please build/run GNUstep with a runtime which supports the +initialize method. The GNUstep stable runtime (libobjc) and experimental runtime (libobjc2), available from the GNUstep website and subversion repository, should both work.
To disable this warning (eg. for an application which does not suffer any problems caused by this runtime bug), please set the GSSilenceInitializeWarning user default to YES.

NASA Decommissions Nuclear Vehicle Research Facility

Bryan Bishop, The Verge:

In 1961, NASA’s Plum Brook Reactor Facility in Sandusy, [sic] Ohio went live, with a focus on researching nuclear-powered vehicles — first airplanes, and then rockets. It was shut down 12 years later, and in 1998 NASA finally decided to begin the process of decommissioning the site. Wired has published a photo tour of the facility, taken before its final demolition on May 31st this year, and when paired with NASA’s own site on the decommissioning process it provides a haunting look at the last days of the 27-acre installation.

Fascinating.

Progress Vs. Regression, Redux

Last week, when the new MacBook Pro with Retina Display was unveiled, the old debate over whether users want “hackable” hardware or not was reignited. I’ve previously added my initial comments to the discussion, but the talk continues–and some fairly dumb things are being said by otherwise smart people. I think the dumbness could stand to be pointed out, because it only diminishes whatever valid arguments they make.

It all started when Kyle Wiens of iFixit published an opinion piece on Wired.com in which he lamented the steady progression away from easily-upgradable Apple hardware. His primary points of contention: this new MacBook Pro follows the MacBook Air’s lead with soldered-in RAM chips, features a battery which is glued to the aluminum case, and is sold with a display which is fused directly to the front glass. These design decisions make for a smaller enclosure, but they also make it very difficult to replace any of the computer’s components. One’s only choice is to have the machine serviced by Apple itself–and if you end up wanting more RAM, for example, you have no options at all. You’d better pay for the extra RAM when you buy the laptop, because even Apple won’t add it for you later.

On the other side of the debate are the Apple-centric bloggers. Here’s Peter Cohen, for example, taking the people-want-simplicity argument to a completely comical extreme:

Clearly many consumers are happy with the tradeoff, which makes for easier use from a wider swath of people who don’t want to be concerned with the myriad fussy intricacies of computer use. It’s not Apple’s fault that the vast majority of consumers who want iPads don’t give a damn about hacking it. Apple’s simply responding to a market need.

He’s right that people don’t want to have to tweak and twiddle with their computer all of the time, of course, and if he’d simply leave his argument right there, I’d be hard-pressed to disagree. However, when he claims that making things user-replaceable makes life hard for the non-geeks, he loses me. Take an iMac, for example. It’s possible that there has never been a computer with more easily upgraded RAM. There is a little door held in place with three standard Phillips screws. Beneath it are the RAM slots. That’s it. How, Peter, is that accessibility negatively affecting an average user’s experience with an iMac? How many iMac users even know that door is there? OK, you might (or might not) be able to argue that this sort of concession to the nerds drives up the price–but you can’t claim that it makes the computer worse for anyone. This same principle can applied to the MacBook Pro: if you don’t want to crack it open, don’t crack it open.

Don’t get me started on batteries. No market has ever cried out for non-replaceable batteries. Can you imagine Joe Consumer complaining that it’s too easy to buy a new battery? It’s absurd. And perversely, maybe no one has benefited from the glued-in battery trend more than iFixit!

The real point to be made here is that the industry is moving this way whether the geeks like it or not. It would be foolish to believe anything to the contrary. But is making that point such a big deal that we’re willing to claim that nobody would ever want to change a battery? Isn’t this sort of blindness just giving the Apple-haters a little ammunition? Won’t they just (rightfully!) point out how flawed your logic is?

It’s Actually a Full-Size, Professional Violin

Don’t get me wrong–I like John Gruber. I think his opinions are pretty spot-on almost all of the time. I’m not sure that’s the case, however, with his takedown of iFixit’s complaints about the non-upgradability of the new Macbook Pro with Retina Display:

Do you hear it? That’s the world’s tiniest violin, playing a sad song for the third-party repair and upgrade industry. And that violin was made by Apple and can’t be disassembled.

His point about this being Apple’s prerogative is taken; I agree with him there. But this isn’t just about third-party repairs. Lots of us want to be able to futz with our own hardware. A nerd like me ought to be able to add RAM to his “pro” computer, at the very least. A fixed, non-upgradable computer makes sense for a consumer-targeted product, but I’m not sure it makes quite as much sense for a “pro” model. I really don’t think this is a particularly whiny complaint.