About a year ago, the project lead for Audacity posted an almost-hour-long video to youtube that goes over their work updating to Audacity 4. It's mostly a PR video, but it does go over their process.
https://www.youtube.com/watch?...

The reason they give is (and I'm paraphrasing and cherry-picking heavily here) that they're making a decision to deliver something useful now, even if it doesn't contain all features, especially since 3.7 is still available. It also gives them a cutoff point so they can start work on completely replacing the core audio engine and deal with Audacity's latency issues.

Everybody talking about giraffes in here apparently hasn't actually checked if common acronyms use their constituent pronunciations. SCUBA, LASER, NASA, ASAP, BOGO, POTUS, PIN, VIN, SONAR, YOLO FIOS, SIM (sim card), FOIA, NATO, OSHA, SWAT, AIDS, GEICO, NASDAQ

Maybe give Neovim a look then.

From the link:
The solution - move tabstops to fit the text between them and align them with matching tabstops on adjacent lines

http://nickgravgaard.com/elast...

People lie. Companies protect their interests. It's Different. https://www.youtube.com/watch?...

If Python encounters mixed indentation, it raises an IndentationError and points you to the exact line the error occurred. If you've got an editor that will run a linter on your code, it'll catch it even before you run. I use vim, so I just use retab, and go on with my life.

Unfortunately, without reading the actual scholarly paper, I can't really say. I can only comment on what made it into the linked article. However, from the pictures, it looks like they're manually defining a mesh on top of each face to perform the image warping. So they would be defining their own mocap dots to track the face image.
You don't have to use the dots, it just makes things easier to track. Check out http://facewaretech.com/ , they do a pretty good job without the dots.

Sorry to double post, but a screencap of an old coworker just showed up in my facebook feed saying "That's my shoulder". The more interesting (relevant) part was the screen showing the facial mocap process where a human is driving the shapes for an alien: https://www.youtube.com/watch?...

Unfortunately this level of the technical process usually isn't documented in public, so there won't be any articles. And it's waaaay over the head of the DVD extras, but some glimpses do sometimes make it through. For instance, I was able to find this bonus clip from The Incredible Hulk showing a pass of the mocap retargeting: https://www.youtube.com/watch?...
Also at 2:05 you can see the mucle set that was used to drive the deformations of the face.

As a professional working on the technical side of 3d animation, I can tell you with 100% certainty that this is nothing new. This technique of scaling the individual parts of the face to match proportions, then applying a muscle simulation is used everywhere. It's how high fidelity, realistic facial mocap retargeting works.
Another good technique is to sample FACS (Facial Action Coding System) style muscle activation data from the source head and just add the individual deformations together on the target head. The proportioning is already taken care of by the definition of the FACS shapes relative to each head.

"Flat is better than nested", so I would prefer the second one. Unless, of course, compute() is an expensive function, because "practicality beats purity".
That said, to me the obvious choice is to use two comprehensions:

mid = [compute(orn) for orn in orns]
borbs = [i for i in mid if i>12]

Fair point about the different types of whitespace. It does require a strict up-front policy. Though having dealt with the differences between VI, Emacs, and Kate (I tried to get him to change editors), I just wrote a quick script that converts, mapped it to a key, and never really thought of it again. To be fair, there wouldn't be a need for that script for other languages.

I have never dealt with compilers, so ... Ok :-)

However, I will disagree with laziness when closing blocks. Having to explicitly close a block when choosing to dedent accomplishes the same task seems redundant to me, especially in well formed code (my view from the other side of the fence!). Anybody can write crap code in any language. Perhaps python makes it easier to write the crap up front, but I can't think of a recent indentation error... But, maybe I just drink the kool-aid too much.

This is an honest question coming from a daily Python programmer. In my experience, I don't feel the required whitespace has left me with bad habits when working in other languages. But then again, my experience in other languages is limited.

What bad habits could come from whitespace being significant?