We can now write scripts using these languages, but is it worth it?

Bash is often my go to for writing shell scripts, and by doing so, it allows me to easily automate a lot of my workflow.

However, the syntax of bash is kinda weird at times, and I often wonder if it'd just be quicker to use a compiled language.

Fortunately, thanks to scriptisto, we're able to use other programming languages such as C, Go, & Rust for writing scripts. But is it any better?

Video Links:

Join this channel to get access to perks:

00:00:00 - Intro
00:01:17 - C
00:04:04 - Sponsor
00:05:08 - Go
00:06:02 - Rust

[mcbot]

v1: script is toe
v2: script is foot
V3: script is leg

[ayaderg]

honestly this is why I just pick a scripting language and learn it more thoroughly, then when I need scripts, I already know exactly what to reach for, and I don't have to futz with a bunch of config stuff

[TheIsraelMendoza]

We like to resolve problems that don’t exist, don’t we?

[kyuthefox]

honestly how is this different from writing a program and compiling it. scriptistoe just takes the file and compiles it for you when you run the file with it. which is nice for fast debugging but its just an compile on execution thing. you could just have a program or nvim macro to compile on file save. and then just run the executable

[segsfault]

8:03 Typo, It's called "ANSI Escape Code"

[THEMithrandir]

Honestly, I hate bash as much as the next person but I don't see much value in this tool. I mostly only use scripts for work and there I have a folder in my dotfiles called scripts that's a collection of makefiles that clone the repo for a script, set it up(compile/make venv, etc) in the repos folder and then add an entry to the path in a script_paths.bash file that's sourced from my bashrc. Makefiles also have a clean option that remove a tools folder and path entry. This way you're more modular, get git tracking for each script individually which makes it easier to share and you can decide on a tool by tool basis what it is you want.

[JohnDoe-nl]

That "Lets give it a <GO> and C how it works, was a spot on intro!😂 I would've added "im a bit rusty" at the beggining.

Cheers

[NexusGamingRadical]

Man pls no bash, save me from string orienated programming i beg

[PhthaloJohnson]

The whole point of bash is that you can use it in the interactive console and the scripts you make in it are run-able across Linux machines. That being said, I would actually use C or Rust for a larger script because bash is awful. It's one of the slowest languages in modern time, its syntax is awful and it's untyped.

[anasouardini]

"I like bash, but the syntax is strange", I'm curious as to why do you like it, since it doesn't have anything special about it, I personally hate it because of the weird and unintuitive syntax.

[antoniocs]

This thing looks nice but as you mentioned in the video it's a lot simpler to do go run or cargo run to compile and run code in go and rust.
For C, if you only have one file, it might be simpler indeed to use scriptisto and not create a makefile

[rafalg]

Shouldn't it be pronounced as a single word with the accent on the 2nd syllable? I was confused when you pronounced it as 3 separate words at 1:09.

[taquanminhlong]

I'm using nushell, it's really a rust version of bash script, it's built with rust as well 😂

[HoussamElbadissi]

Heyy it's great to see your face! Love your content, keep it up!

[Richard-cksr]

Very nice. TCC from Fabrice Bellard has this feature for C - see ex1.c ex2.c.

[IgorPetruk]

Omg lol, that's my tool. Thanks for making this video!

My inspiration for writing this was a desire to write block scripts for i3bar in rust. So I can fetch deps transparently to access various data sources, Internet libraries.

It is not packaged to Debian. And another tip is to use built in templates via `scriptisto new` so you don't have to write the build comments from scratch

[Willowskh]

All the language listed are all good for scripting, I don't really get the reason for saying that it's not suitable? If 'go run' command is already good enough, doesn't it only mean an external library like (scriptisto) is just adding unnessary dependencies / libraries to your project?

[fabricehategekimana]

Tbh, I use nushell as my shell and scripting language. This is the first language in my life that make building CLI tools easy. With the GUM CLI, the interface is next level

[nickolaierlan]

BunJS shell feature is a charm, I use it as a bash alternative

[svaira]

This seems rather complicated tho. TCC works fine for C scripts since forever and has the benefit of not having to add configs etc. Obviously it only works for C, and there only for C90 and a subset of C99 (although honestly I don't use VLAs anyway, which I think is what they didn't implement, so it's fine for me), but for that it seems like a better alternative if you don't rely on some specific gcc or clang-specific intrinsics.