I was thinking the same thing…

Yeah, I'd just use any of the available script languages instead, this just seems tedious

If bash wasn't a problem, we wouldn't have developed a billion scripting languages. Small bash files probably have more bugs then a large C project.

programming is about solving problems so programmers are problems solvers they sometimes create problems too in order to (re)solve those problems

What if we made a scripting language none of the things good about a scripting language. If you want to write scripts in C, compile a fucking executable 🤣

I haven't used it myself but as far as I can see it: - Only recompiles it if the source code has changed (keeps hashes of source content) - Allows for extraneous build artifacts such as Cargo.toml to be included in the metadata to retain the one file nature of a script - Allows you to just give someone that opne script file and as long as they have scriptisto installed it should work for them too Still not sure it is for me. I'm too used to bash and Perl and see development in C and Rust to be completely different mindset.

@@grifferz so it's like Cmake or any other build tool, but it forces your files to stop being language compliant by forcing you to add the # at the top of the code. Cool. Useless.

@@tiranito2834having everything in one file is great for ephemeral scripts.

Not to mention a compiled exe will work on more than one person's machine. Isn't half the point of scripts that other people can easily run them?

@@Waffle4569 Yes, but what if you wanted something that the user could make changes to for configuration purposes. Storing everything in json or similar files isn't enough for all configuration needs.

Exactly

That sentence rubbed off on me as weird. I thought the major reason to like a scripting language would be its syntax

The main reason is it's portability and conforming to the POSIX standard. Apologies if my statement was unclear. Syntax is usually only one of many considerations when it comes to my preferences!

You probably think that way because you compare it to the wrong thing. It all starts to make sense once you realize that `echo "Hello, $USER"` is not Bash's way of saying `print(f"Hello {user}")`, but rather `subprocess.run(["echo", f"Hello, {os.getenv('USER')}"])`. The whole language is build around interactive use first and foremost, to quickly invoke programms on a system. Scripting is more of an afterthought that had to be made to work around it.

It's just syntax. Bash is everywhere and that's why you have to know it if you call yourself a real engineer instead of "react dev". Just like awk, sed and other linux cli tools.

@@SkyyySi It's not only me who finds Bash's syntax so ugly, and also your code starts to smell as soon as you start introducing functions to it. My Linux's post-installation script is written in TS and Bash for the same reason.

Bash content incoming soon!

Have you tried dash?

try perl bro. perl is a great scripting language

@@harleyspeedthrust4013 oh god no

@@trevorb5516 hey man don't listen to the rumors. perl is awesome

@@harleyspeedthrust4013 are you kidding me

Nushell is great. All of the power and interactivity of the CLI, none of the strangeness of bash.

Nushell is love, nushell is life

😭 I actually may have found another solution!

There is this new language that compiles to bash so maybe give it a look

@@flamendless I think it's called Amber Lang.

the wrong .. code wrong ..

Ever try Tcl? The language where everything is a string?

Thank you! Will do!

@@dreamsofcode Talented, Funny AND Handsome?! You really are the trifecta- amazing work, mate!

Yeah, and if you use cargo as intended you get other benefits like rust-analyzer understanding your dependencies.

how is scriptisto faster than writing "gcc script.c -o script" ? on another note: how is scriptisto faster than writing a 1 line makefile with the exact same compilation command? if you're going to be making some small scripts, it's orders of magnitude faster to do any of those 2 things than using scriptisto, lmao...

I partly agree, but why not learn makefile instead of another scripting language that injects itself into your code?

I guess the idea is to keep it similar to the benefits of a script, such that you're able to contain everything you need in a single file.

I also prefer to compile things when i can for scripts that require thoughtful planning - but for repetitive things where a single file is good enough, running feels faster than build + run even if not compiled

`cargo r` Runs it, compiles it. Copy the binary at will. I really don't see the point. Now, if we're talking a language that can actually do more with a couple of lines of code, like Python or Ruby, sure. But for Rust?

It might be nice for a small script you make small tweaks every so often, since the code is visible in the same place that you run it from. Also I'm to lazy to right docs so I often `cat` out the script to make sure I'm running the right one or what args it needs. It is a skill issue but whatever.

@@dreamsofcode You mean like Go? LOL

They're hit or miss depending on the language. For Go, it kinda works due to the $GOPATH, although the actual shebang causes a constant error. For Rust + C, then it's not good.

Look who's there!

Thanks dude!

Sorry if that line wasn't clear. Using Go with scriptisto I don't think is the best, instead I much prefer to just use `go run`

Yeah, definitely better. The Rust example was terrible, better write the code and let cargo build or just use Go anyway.

Thank you! I'm definitely older than I look tbf! I think bash is one of those skills that I personally should know better, if you asked me to write a for loop without any reference, I don't think I could achieve it!

I also thought he is around prime's age

Me and catppuccin have broken up 😭

@@dreamsofcode :o whyyyy

@@dreamsofcodewhat's the new theme?

@@christopherwood6514 Tokyo night! I'm enjoying it a lot at the moment.

@@christopherwood6514 Lol replied from my other channel!

I'm excited for #!/usr/bin/env cargo

Even normal zig trips me up 😭

"YAML key values"

@@jasiek1309 Thank you!

It's definitely a fun project, and worthwhile of a try in my opinion. I'd be interested to know what you build with it!

Agreed. Python is pretty good. I find it becomes a bit heavier once you need to use dependencies, but until that point it's a great choice for scripting.

@@dreamsofcode Agreed, dependencies are a nightmare in python lol

@@Mempler Not just dependencies, but also python versions

@@dreamsofcode will consider using Scriptisto to solve that problem for Python too. They have a python-pip template.

Doesn't poetry solve this problem?

I think I came to the same conclusion at the end of the video :)

Which language did you choose? Maybe I can do a follow up 😁

@@dreamsofcode *Takes a deep breath* So note this on a Nobara/Fedora machine and likely will be used as an automation server when put out to pasture when I update my machine, so for my use cases, I expect frequent changes, but it can be local over a network. And when I get my gaming machine, I will likely stay with this family of distros. I chose Nim and D. I like nimscript and rdmd. I like Nim for the python-like syntax and the powerful out of the box FFI. I like D for getting me out of my fear of curly bracketed C languages (maybe rust is next, **shiver** ); but more seriously for the speed and general use standard library. It has basically everything I need including edge cases for complex numbers, I/O, networking and HTTP, as well as being designed to be very 'generic and flexible'. I even compiled CPython recently and it wasn't particularly slow. For a command and with a spotty connection after all, one it was all on my machine, it works out of the box lol. So yeah, good videos man! Keep it up, and be sure to spread good technical and personable knowledge you can. 💜 Edit: Oh and I compiled MRI Ruby, which has a C based and it was much faster and smaller and I love Ruby! It was my scripting language of choice when I got here, and I owe it alot.

@@dreamsofcode I chose Nim (nimscript) and rdmd (D) for any scripting job in near and long term. I like Nim's python like syntax and since I expect to be doing alot of tinkering with CPython and MRI Ruby source (both of which I just compiled), it's C FFI interop is kind of smooth. I like D's huge standard library for out of the box functions and jobs you can do. Really, and since rdmd exists as a companion to the compiler, anything you can do with the standard library can be piped to your shebang shell. It is also got me over my fear of curly bracketed languages like C and Rust lol.

I am not sure if my comment got filtered twice, so last try, I picked D and Nim (rdmd) and (nimscript)

@@twenty-fifth420 This one made it through! Nimscript is an interesting prospect to try out!

Absolutely! I'm also doing some twitch streams as well

It's hit or miss depending on the language. For Go it worked pretty well, but for Rust it would break.

​@@dreamsofcode I heard that there is an RFC rust script currently im its work. Hopefully that would make things really intresting

I think I may have found just the language 🤞

@@dreamsofcode Please, do share. Lemme have a look :D

Thank you!