Based on my luck at finding a good text diff tool on iOS, doing text diff must be the most difficult task in the universe. Is that was diff stands for? Difficult?1
There once was an amazing iPad app called Kaleidoscope that was beautiful and did an outstanding job of comparing text files, but its makers stopped updating it long ago and now it isn’t even on the App Store anymore.
Clearly this means I’m finally going to have to learn how to write iOS apps like I’ve been saying I was going to since 2008 and make my own text diff app.
This could cost me a few years of life I don’t have.
Sorry. That’s a very difficult joke. ↩︎
iOS 14 beta is remarkably stable and performant, but running betas always carries a risk that a subsequent beta version will break something important to you. iOS 14 dev beta 2 (and public beta 1) broke some fundamental actions in Shortcuts – Split Text, Combine Text, and Change Case.
Because I have several shortcuts that do a lot of text parsing, not least of which are my blog post and podcast episode publishing shortcuts and helper shortcuts, I noticed this immediately. It didn’t take much troubleshooting and testing to realize that these three actions now return nothing regardless of input. They’re just completely broken.
The good news is (also thanks to changes made to Shortcuts for iOS 14) it’s very easy to create a folder for iOS 14 beta specific versions of your shortcuts, make copies to that folder, and then fix them. Folder …
I do a lot of work on my iPad and I don’t normally advocate diving into iOS betas in general anyway. And even though my iPhone isn’t as critical to me now as it was before I really got into modern iPads, I still need it to last through the day and generally be stable. So you might think I decided to avoid the iOS and iPadOS 14 betas like the plague.
Narrator: He did not avoid the iOS and iPadOS 14 betas like the plague.
The funny thing is that while Apple didn’t mention performance and stability at all during the WWDC 2020 keynote, iOS and iPadOS 14 are quite performant and very stable, remarkably so for any beta let alone the first beta. It’s about as far from last year’s iOS 13 beta experience as you …
I’ve been doing a lot of website testing lately as Vic and I work together on a podcast theme for Hugo. Part of website testing involves using the element inspectors and developer tools available in most (all?) desktop browsers. Sadly (I thought) I couldn’t do this in the same way on iPadOS, which I spend a huge percentage of my time working in.
I was wrong.
Inspect Browser is one of those third-party iOS apps that proves that while Apple may not care much about enabling people to get real work done on their “Pro” devices, the people out there doing the work do care.
The developer of Inspect Browser claims on the website that their app provides desktop-class web development tools and features, and they are not kidding.
Remember not too long ago I had to confess my regular expressions deficiencies to you, the dear reader, regarding an overly verbose regular expression I needlessly crafted, not realizing the greedy nature of the RegEx rendered part of it completely unnecessary?
It happened again.
This time it happened to me with a regular expression that I’ve used many times before. It has to do with my blog posting shortcut(s) and how I handle parsing markdown footnotes in iA Writer documents.
Here’s the regular expression I was using to find footnotes in my iA Writer texts:
My thinking when I wrote it is that it would find anything starting with [^, followed by one or more of any character, and ending in ]. Which it did, and it usually did it the way I expected it to. But then one day I typed the following paragraph: …