Daniel Jalkut:
Over the years I’ve had a lot of ideas about how FastScripts might evolve, and have worked on new features intermittently. As part of my recent decision to reinvest in Red Sweater, I decided to focus on finally shipping some of those features in a major 3.0 upgrade. Today, I’d like to share what I’ve got so far, as a public beta[…]
[…]
The major changes in this upgrade are the introduction of a search feature so you can easily sift through all the scripts in the menu, and a major overhaul to the way scripts are executed so that multiple scripts can be fired off in rapid succession without interfering with one another.
[…]
Apart from the changes listed above, I hope to soon offer the ability to monitor and cancel long-running scripts are launched from FastScripts.
This great app is free while in public beta. I’ve been using the beta for a several days with no problems.
Previously:
AppleScript FastScripts Mac Mac App macOS 11.0 Big Sur
Joseph Heck:
One of the interesting take-aways is that the terms “safe” and “unsafe”, or at least the specific implications of when they’re used in the swift language, are broadening what they cover with the upcoming changes. You could start to see it as early as last October when the Swift Concurrency Roadmap was published, but the wording wasn’t fully in place, more of just conceptual frameworks. The details of the broadening of the definition didn’t hit home for me until I caught up with the recent discussion on the pitch for task local values.
[…]
Across the recent pitches and proposals, some of the language terms that use safe are now being used to imply concurrency safety, somewhat independently of memory safety. The goal looks to be to provide APIs that have some guarantees about thread-safe access and updates. And along with the safe versions, there are some potential “unsafe” variants to use when you need the escape hatch and are willing to take on the thread safety guarantees yourself.
Paulo Andrade:
If you’ve ever encountered the dreadful UnsafeMutableRawBufferPointer or one of its friends and ran to stackoverflow… then this post is for you!
Previously:
Concurrency Language Design Programming Swift Concurrency Swift Programming Language
Jason Snell (tweet):
Here was my bad idea: Just because MailChimp’s RSS system didn’t work the way I wanted it to didn’t mean I couldn’t make it work the way I wanted it to. I could set MailChimp to automatically mail out an email on Friday evenings to all Six Colors subscribers, based on an RSS feed.
And then I could write a script that would generate an RSS feed with a single entry, containing exactly the newsletter I wanted to send.
[…]
Though there are some ways to parse RSS feed using the System Events app’s built-in XML parsing, it’s unreliable. Instead, I turned to the JSON format, which is much easier to work with, thanks to Mousedown Software’s excellent app JSON Helper, which converts JSON feeds into AppleScript objects.
AppleScript JSON Mac macOS 11.0 Big Sur MailChimp Mailing Lists Programming RSS WordPress
Tom Hallman Jr. (via Hacker News):
“He saw there were old World War II teletype machines not being used,” said his daughter. “Another deaf engineer in California had come up with the way to send signals over phone lines. My dad came up with the coupler component the teletype needed. He then pressed Western Union to provide the old machines to deaf people and Bell telephone to use them on their lines.”
As rudimentary as it may seem now — both users needed a machine to type messages back and forth on what was called TTY, Telecommunications Device for the Deaf — it was as innovative when it launched in the 1960s as text messaging was when smart phones entered our lives.
[…]
In addition to teaching, Taylor advocated for a national operator relay system for the deaf to allow them to communicate with people who were not deaf and did not have a TTY machine.
Accessibility Federal Communications Commission (FCC) History Rest in Peace
