I miss the old iTunes 10 interface, which I use as a database manager (I like smart playlists, playlist folders, and Genre > Artist > Album columns).
AppleScript because it has so many APIs. BetterTouchTool makes heavy use of it. I taught myself how to code in it when I was 13, and I still use it now.
You mean the commands you can use on apps like iTunes, Finder, Photos, etc.? Those are not AppleScript-specific per se (AFAIK there used to be an option to write Automator scripts in JS). You'd need the Linux/Gnome/KDE equivalent of the Open Scripting Architecture ( https://developer.apple.com/library/archive/documentation/Ap... ) with active participation from app developers. Sounds like a huge overtaking.
Yes, it would be a huge undertaking. I've already rewritten my own apps for offline maps, calendar, notes, and I plan to write contacts and iTunes too. When there's a standard API comparable to Apple Events/OSA within those core apps, I'd hope to have enough leverage to persuade other app developers to accept pull requests.
We already have D-Bus to cover sending events to applications, what's really missing is a standard way to enable scripting. I've had a similar idea myself but never got around to implementing it, but I think a standard D-Bus interface applications could implement to expose a scripting dictionary along with a Python/Ruby/Whatever library to implement a more OSA-like interaction would go a long way.
AppleScript because it has so many APIs. BetterTouchTool makes heavy use of it. I taught myself how to code in it when I was 13, and I still use it now.