You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace the awkward dual programming language setup (shell and AppleScript) with Swift, a higher level programming language.
Or Go, if the various macOS libraries aren't too difficult to work with from Go. Go prepares us to eventually support Windows and other platforms besides.
That will make it easier to introduce new CLI flags.
Potential to recombine both applications into one application.
We'll also be able to replace the external ImageMagick CLI tool dependency with an image (cropping) library.
Both tigris and euphrates currently depend on bc, awk, and findutils. These happen to come with macOS, though moving that logic into a general purpose programming language like Swift or Go, aids in futureproofing (in case macOS later removes these from the default package set) and cross-platform support (other operating systems use conflicting CLI flags and conflicting default package sets).
We've been on track to need four scripts, due to the quirks inherent to both POSIX sh and AppleScript. General purpose programming languages help us accomplish more, with less code.
The text was updated successfully, but these errors were encountered:
Replace the awkward dual programming language setup (shell and AppleScript) with Swift, a higher level programming language.
Or Go, if the various macOS libraries aren't too difficult to work with from Go. Go prepares us to eventually support Windows and other platforms besides.
That will make it easier to introduce new CLI flags.
Potential to recombine both applications into one application.
We'll also be able to replace the external ImageMagick CLI tool dependency with an image (cropping) library.
Both tigris and euphrates currently depend on bc, awk, and findutils. These happen to come with macOS, though moving that logic into a general purpose programming language like Swift or Go, aids in futureproofing (in case macOS later removes these from the default package set) and cross-platform support (other operating systems use conflicting CLI flags and conflicting default package sets).
We've been on track to need four scripts, due to the quirks inherent to both POSIX sh and AppleScript. General purpose programming languages help us accomplish more, with less code.
The text was updated successfully, but these errors were encountered: