![]() So if the runtimes aren’t available by default, does that mean that Automator won’t have a Run Shell Script action anymore? Or, very likely, that Automator will be no more, replaced by Shortcuts and entirely lacking scripting runtimes? It’s potentially a lot of work for him with no apparent benefit to him or the users of his code. I would be surprised if you can embed a runtime within a workflow so even if he ports all the scripts to a single language, first installing that scripting language will be a system requirement for their use. Even within Markdown Service Tools, one project, he has used more than one scripting language within its Automator workflows. They’re basically little programs for people to use without knowledge of the scripting languages themselves, at most you need to know the fundamentals of running code in Terminal. From there, Homebrew can include the Rudy runtime so all its formulas don’t have to be rewritten.īrett’s collection of projects is an example of the “vast corpus of code” I referred to when I originally posted this news to the list. Homebrew’s current installation method requires Ruby to already be present on a Mac but I don’t think it will be difficult to change the installation method to not require Ruby. So why is Apple moving in the opposite direction? These runtimes were even touted as a selling point in the past, and Microsoft is just now starting to add tools like this to the default Windows install. They’ve not been great about keeping the runtimes up to date, but that’s actually been a boon, requiring less effort to keep scripts working with every OS release. So the question is why? I can’t wrap my head around any real benefit to Apple’s line of reasoning on this. I’m sure we’ll all figure it out, but I’m also convinced that it’s an unnecessary burden on developers. Dropzone, for example, uses Ruby as the base for all of its Destinations, and embedding Ruby in a way that makes it useful to the general population is not a simple task. Some apps rely so heavily on system runtimes that they’d be crippled without embedding their own runtime. Marked makes use of the system Ruby runtime when it compiles Scrivener documents for preview, and many of my customers use Custom Processors that rely on scripting runtimes, even if they have limited experience in the shell. Don’t forget, even Homebrew requires Ruby to install itself, so that’s a speed bump to easily installing command line tools. Feasible, but unlikely that I’d ever get around to updating everything that uses bash scripting at its core. I’m unclear as to whether bash will be removed from the default install entirely, but doing so would also require many of my projects to be re-tooled for zsh so as not to require every user to install bash just to run a simple shell script. The announcements also include a switch from Bash to Zsh as the default shell. Brett Terpstra has penned a blog post about this as well:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |