Recently I added sounds to a website that fall into this non-essential but experience enhancing (imo) category. I've had somewhat mixed response to this, from total annoyance to utter delight. I'm really not sure what the best approach is to take with sound on the web.
edit: Sounds are present when opening the console, or dragging a canvas around
Since jq is sed for JSON, by the transitive property, you're saying that sed is not Unix-y. ;)
Seriously though, I use both, and IMO they serve different purposes. gron is incredibly useful for exploring unknown data formats, especially with any form of
something | gron | grep something
Once you've figured out how the data format in question works, a jq script is usually more succinct and precise than a chain of gron/{grep,awk,sed,...}/ungron.
So in practice, gron for prompts and jq for scripts.
I mean, you can pretty much already do that with AWS, and with hourly pricing to boot. It might be nice to have something configured for easy integration into an ldap authentication mechanism, but I imagine you could get a base image built for a company fairly easily.
I'd love that as well. It's certainly something I'd like to implement... but as of yet, I haven't come across many use cases (personally) in which it's necessary.
That said, I would definitely accept help in adding event-driven rules!
I can certainly see where you're coming from. Many of those people would probably benefit from Hazel more than Maid, however. :) As it stands, Maid is somewhere in between hand-crafted shell scripts and a user-friendly GUI (but definitely closer to the former).
That said, Maid has certainly helped me out, and I'm happy that so many others have found it intriguing. (Thanks for the comments!)
I used to use bash scripts and `find` for the purposes that you give. Maid came about when I was starting to add logging and a "dry run" option to those bash scripts. Ruby quickly became an attractive option then. But for many one-off tasks, I still find knowing how to use `bash`, `find`, etc effectively to be important.
There are other benefits beyond logging and an easy to invoke "dry run" option. For example, many of the methods in the DSL give back arrays and strings, any of Ruby's many Enumerable methods are available to you. If you have any difficult-to-express logic, that can be quite handy. Also, not every OS keeps its trash at `~/.Trash`, but Maid will do the right thing on OS X or Linux.
There are other reasons you might prefer Maid over shell scripts, but in general my hope is that Maid can provide a common framework for these types of scripts and also a community for people interested in automating tasks like this.
Maid (and Hazel) certainly aren't for everyone. The original intent behind making Maid was to automate part of what drivebyacct2 describes. I just got tired of manually doing things that could be easily automated. :)
Maid isn't only for cleaning up Downloads, etc. -- it may even be helpful for drivebyacct2 to organize things in other ways. For example, this is a Maid script I've reused many times when handling SRT files for videos:
https://garden.bradwoods.io/notes/design/juice