automa VS fish-shell

Automa open source tool to automate connection request on linkedin

I was able to make this happen by using a chrome extension called automa. Download Automa Here is a link to my workflow using that extension: Download

I use Automa for repetitive web searches. I'll use the integration with Google Sheets to pull whatever column I'm needing, loop through the data, run a script looking for specific anchor tags and save the href values into a table that can be read / exported once the automation is done running.

Automa [0] is just another no-code extension to automate browser. I used it to scrape excel files from the website of an open-end fund, which does not expose public API for its daily NAV historical data. This extension not only saved me time to manually point and click 1000s of url, but also give me a reason to procrastinate teaching myself selenium.

[0] https://www.automa.site/

Interesting, I don't know javascript though. In chrome I use the Automa extension, which is connecting lines with blocks (and you still have to pick up some js. I didn't even know what an 'element' was when I started). Even a beginner can do something useful after an hour of study or so. YMMV.

https://github.com/AutomaApp/automa

https://docs.automa.site/

There's a library of scripts you can copy from

https://www.automa.site/workflows

Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.

https://github.com/fish-shell/fish-shell/releases/tag/3.7.1

https://github.com/fish-shell/fish-shell/issues/7772#issueco...

https://gitlab.archlinux.org/archlinux/packaging/packages/fi...

A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123

An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust

It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/

And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123

We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.

They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.

[1] https://github.com/fish-shell/fish-shell/pull/9512