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

[@dreamsofcode]

To try everything Brilliant has to offer-free-for a full 30 days, visit brilliant.org/DreamsofCode . You’ll also get 20% off an annual premium subscription.

[@mcbot6291]

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

[@TheIsraelMendoza]

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

[@DevOpsLee]

I was thinking the same thing…

[@CottidaeSEA]

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

[@PhthaloJohnson]

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.

[@phatboislym]

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

[@Waffle4569]

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 🤣

[@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

[@grifferz]

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.

[@tiranito2834]

@@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.

[@Avbanks23]

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

[@Waffle4569]

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?

[@hughesd.mungus9819]

@@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.

[@whisperpone]

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

[@NexusGamingRadical]

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

[@dreamsofcode]

😭 I actually may have found another solution!

[@flamendless]

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

[@jordanlowell688]

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

[@microsuxx]

the wrong .. code wrong ..

[@j-r-hill]

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

[@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.

[@plutack]

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

[@dreamsofcode]

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!

[@SkyyySi]

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.

[@boccobadz]

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.

[@anasouardini]

@@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.

[@segsfault]

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

[@debajyatidey9468]

Exactly

[@JohnDoe-n7l]

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

[@rafalg87]

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.

[@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.

[@josephbrandenburg4373]

Have you tried dash?

[@harleyspeedthrust4013]

try perl bro. perl is a great scripting language

[@borogove-n6e]

@@harleyspeedthrust4013 oh god no

[@harleyspeedthrust4013]

@@borogove-n6e hey man don't listen to the rumors. perl is awesome

[@reinhold1616]

@@harleyspeedthrust4013 are you kidding me

[@taquanminhlong]

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

[@EpKjelltzer]

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

[@RealYethal]

Nushell is love, nushell is life

[@THEMithrandir09]

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.

[@antoniocs8873]

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

[@ovidiu_nl]

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

[@tiranito2834]

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...

[@NetherFX]

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

[@BrazenNL]

Why not just compile it?

[@dreamsofcode]

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.

[@mysterry2000]

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

[@BrazenNL]

`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?

[@Rozenmorte]

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.

[@synen]

@@dreamsofcode You mean like Go? LOL

[@KaiAbyss]

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?

[@HoussamElbadissi]

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

[@dreamsofcode]

Thank you! Will do!

[@saperelearns2077]

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

[@IgorPetruk1989]

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

[@joshuarobert7192]

Thanks for the good work man!

[@DynamicalisBlue]

I’m not the biggest fan of bash and do prefer C but that is just too much boilerplate for a script. Surely Python would be preferred.

[@bastiana3611]

6:37 How come it uses Rust edition 2018 instead of 2021?

[@Richard-ck7sr]

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

[@LunarLambda]

I wrote my own C-script shebang tool in bash. it's fun Rust is getting `cargo script` maybe sometime this year, which will allow single file packages that can use dependencies and stuff

[@Inyourface3445]

if you pan on using a script you made for a long time, and using a compiled lang, just compile it once and move the bin file to the /bin directory in linux (or another dir that is in the path)

[@fabricehategekimana5350]

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

[@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.

[@JasonMitchellofcompsci]

As a side effect this is going to put build information inside of source files. THANK YOU!!!! Imagine a future with no build files because the source code has the information needed to build in it. And all build systems know how to leverage it. Also, your speech is very good. Solid elocution.

[@oblivion_2852]

For single file scripts this is pretty great. It's like an inline makefile/build script

[@solvecode]

You're an inspiration. I use almost all the tools youve suggested. And You're one of those who inspired me into making my first video myself. Man ypu must spend a lot of time editing. Thanks!

[@nickolaierlan8064]

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

[@bastianwegge]

Looking forward to hearing about bash & how you‘re doing automation 🙌🏻. Keep up the good work!

[@dreamsofcode]

Bash content incoming soon!

[@secondary-smiles]

The nix-shell shebang is another powerful way to improve or even replace this tool.

[@ryzechdev]

Rust actually has a scripting feature built in! It’s in the nightly compiler but it works basically the same, and much easier

[@_Verac]

I use quickjs + bash. Js for complex data structures, and bash as a wrapper for the js script.

[@theangelofspace155]

6:00 why is not the best? Can we just run the script with go run, and called with a bash script only run `go run my_script`? Or just add a alias to the shell for it?

[@dreamsofcode]

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`

[@software_engineer_business_man]

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

[@TymexComputing]

Dont get whats extra while writing and running the app as a script? enumerating the ENV?

[@konstantinsotov6251]

this gave me an idea to write a header-only library for C that will have tools to make scripting easier...

[@timseguine2]

I've never tried it by why wouldn't writing "go run" in the shebang work for golang? Something similar works for python

[@ricky2629]

I don't understand the usecase for this at all, but it's neat that it exists i guess. I'm gonna stick to either just use bash or compile beforehand and use the binary when needed.

[@dreamsofcode]

Yeah I agree, it's certainly not for me. That being said, having strong types in a script does feel nice, but I don't think this is the best way to achieve it.

[@heroe1486]

Making KZbin content, that's what most programing videos are about, showing unrealistic stuff just for the sake of getting engagement

[@hansdampf2284]

Am I missing something? How is that better than compiling a program and running it? I could do this with a simple make target

[@PS3PCDJ]

"Entr" can monitor changes and run specified commands once a change is detected like a makefile, which itself will know what to recompile based on what changed, rendering this entire program pointless.

[@ACium.]

At 2:28 , add what? I didnt hear properly. Yamokey value?

[@jasiek1309]

"YAML key values"

[@ACium.]

@@jasiek1309 Thank you!

[@NetherFX]

The only difference now is that you don't need to compile/build a program. So what does this solve exactly?

[@ddanier]

For writing well structured shell scripts I can only recommend using nu shell. This is a completely new shell which has typing, scopes, modules and many more modern features. No need to stick to bash or similar. As with bash you don’t need to change your default shell, just use a shebang at the beginning of your scripts. I can highly recommend trying this instead of fiddling with c/rust/go for scripting. 😉

[@conaticus]

Great vid as always

[@dmitriidemenev5258]

Look who's there!

[@dreamsofcode]

Thanks dude!

[@jackzugna5830]

Maybe for some situations you can use C+Lua or C++ with Sol (Lua lib). You can create a set of specific functions in C and call them from Lua, compile the whole thing once, and only edit the Lua file according to the project. I think this is the best way to get scripting speed and natively compiled code performance.

[@Fudmottin]

The next step down the rabbit hole is to set Emacs as your $SHELL and do scripting in Emacs Lisp.

[@pyromancerforhire]

What's the difference betweeen using this, and simply compiling and adding the executable to your enviroment? When I built a silly wannabe git to learn Rust I had a makefile copy the compiled executable into my local bin for execution from anywhere in any terminal. I'm genuinely curious

[@Lars-ce4rd]

This seems totally unnecessary. Also, I'm assuming it has to recompile your code on every init or implements a cache for the compiled binaries. Anyway, it seems like basically the same as compiling your own code, you even have to write the build command anyways. So yeah, I don't see the value, I'll probably just stay away from this

[@theairaccumulator7144]

He says it caches the binaries and uses a hash to know when to recompile. Otherwise the rust example would take half an hour each time he invoked it. Imo it's pretty useful since you don't need a whole build setup for 1 file.

[@borogove-n6e]

I use javascript and node, and have found myself reaching to it for scripting as well. I find it a bit hilarious that it actually works more seamlessly than go for this purpose.

[@vikingthedude]

Do the go/rust LSPs work with these scripts? I imagine the lsps wouldn’t know where the dependencies are stored

[@dreamsofcode]

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.

[@lucascqueiroz97]

Can you share your tmux config to set the window number to that symbol? Tried to find in your GitHub but the config there looks outdated?

[@sebas11tian]

Scriptisto is an Esperantism I am sure.

[@hydra147147]

Once cargo script RFC lands there would be no need to do this in Rust with external tooling

[@dreamsofcode]

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

[@dipi71]

Ruby with its gems (Paint for coloured output, for example) is clearly the best and most fun option. So it's been in my case for over 20 years anyways.

[@suchithsridhar]

It seems like a complex solution to a simple problem. Bash works for a simple sequence of command calls and python for anything more complex. Languages like C, Go, and Rust aren't designed for scripting and will lead to more problems. You can install python packages globally using your package manager. If not create an environment called global and install packages there.

[@akemrir]

Hi, video is quite nice, but it lacks consistency. Every presented language with different example? And only last was used with template from scriptisto? Go template also has colouring dependency put into go.mod. In general this is overkill. They can be compiled easily to binary which can be shared. These scripts need specific compiler and scriptisto on the machine, so you cannot give them to everyone.

[@1ups_15]

I'd definitely use this to make cpp scripts if it didn't take ages to compile

[@IgorPetruk1989]

It will compile and cache the result. The second run if you haven't changed the file will jump straight to the binary with barely any delay

[@dirty-kebab]

I wanna say, I'm not a fan of seeing people. Like the content should speak for itself, and yours does! Like Fireship

[@dreamsofcode]

Haha thank you.I've moved towards a bit of face footage in order to speed up my production. I'm still a solo video creator and I have so many video ideas that I've gotta figure out how to speed it up a little.

[@dirty-kebab]

Speeding up production? Oh that's a great reason, I hadn't even considered it!? 🧠

[@opposite342]

use anything tbh I went from python to some nim and bash for small little scripts to help setup my environment (for me I'd only use bash for really really not complicated scripts, and then for whatever else that's around medium size it's probably nim)

[@halavich9672]

Hey! Very much in time, yesterday I just started multibin project of rewriting some of my scripts to rust. Quickly I realised I need to have it go with dynamic library, as bins are kinda large otherwise

[@PouriyaJamshidi]

You could use Nim, a compiled language with Python-like syntax, which comes with Nimscript.

[@Windeycastle]

What is the reason to use this? To me, it feels more complicated then just writing pure C/Go/Rust and compiling it yourself. Bash often does the trick, and if speed is an issue, well, you're not really scripting anymore at that point, and a compiled program shouldn't be too hard to make then.

[@dreamsofcode]

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

[@roganl]

A tool is a tool is a tool, to abuse Gertrude Stein. So many technologies are tools in search of use cases. I am glad to hear you want to produce some bash content. I was flabbergasted to see your face on a video - from your voice I had imagined you being at least 40 - you come across as very well seasoned. Excellent content - as per usual.

[@dreamsofcode]

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!

[@daphenomenalz4100]

I also thought he is around prime's age

[@gosnooky]

I feel this is the best use case for Python. I use it all the time for certain tasks and use as few external dependencies as possible.

[@hardas81]

Am I missing something? What was the point of all this? You're wrapping the compilation & execution of a perfectly working source file in a script? What do you stand to gain against having a Makefile or running cargo build/run?

[@dreamsofcode]

I'm pretty sure I brought up similar points.

[@Igor-zh9ds]

Anything is better than makefiles. Instead of a makefile you could use this to write your own build system

[@greensheen8759]

I like awk cause it's both a command AND an entire programming language. It's great for processing CSV data too

[@ed223-p5g]

when i want to run a script this is the last thing i want, with python i just create the virtual environment, install dependencies and i'm done while you're still configuring this tool

[@angeldude101]

Compiled scripts are nice for speed, but they can easily be _much_ larger than an equivalent bash script without some pretty extreme measures. For actual scripts, I'll probably be using nushell for the most part for the foreseeable future. Also considering that my user and system environments are themselves effectively "compiled", there's really no overhead to just writing what would be a script in Rust or C and then just compiling when when rebuilding the environment. There are even standard functions specifically from making compiled scripts. I thought I remembered there being one for C, but I was only able to find one for Haskell, and a function to generate these script compilers. (Edit: found the C script function.)

[@_liminor]

was it an intentional pronunciation choice? i'b betting the akshual way was supposed to be akin to virtuoso "skrip-tee-sto"

[@Dyils]

Why does he pronounce everything like that "She-bang", "Script-is-toe" wtf :D

[@MXS77]

Pls tell your alacrity window size

[@coyo_t]

i love how they have a template for java even though java 22 has made it pretty easy to run a directory with just the java command now v_v

[@EliteTester]

tcc also has a -run flag to run C files

[@ika_666]

is it a script if its compiled anyways?

[@jongeduard]

Really cool project, people make amazing things. But for me I still doubt if it has a practical use case. You still need to install the whole thing as a dependency, scriptisto. And one reason why I also use a lot of Shell or Bash scripts is that it's far more standard on every Linux distro. Bash is installed by default, nothing more is needed. Shell scripts are also much simpler for actual system tasks, I mean when executing external commands is actually my primary goal. Good to mention is that Python is also pretty standard on Linux (maybe not on a fresh base Arch linux install, but tons of additional packages have it as a dependency), so I have used that for some system related scripts too, as it is very simple and also stored as a text file that does not require compilation. But for most actual system tasks it is still often more code to write, and shell scripts stay a simpler default in many cases. So real programming languages do I use for actual software development, both at work and personally, when actually building things.

[@thejezzi5219]

I'd use python as it is already installed on most linux distros and on macos (not sure about windows though). It has everything you need out of the box and scripting feels more natural.

[@kevinmarques9334]

Such a good video. As a Bash enthusiast my self, I can't wait for your future Bash related videos 👀

[@DNFINST]

I had been using fedora for years and never had an issue with pip. Then I got bored one day and installed Debian and it yelled at me about virtual environments. I read more about what's happening in fedora and just went back to it to never have to deal with that out of the box again.

[@CyberSamuraiX]

And here I was trying to learn Go as a replacement for my automation with scripts/packages in Python :p

[@mohamed1208]

I never expected to see the face of the ephemeral/dreamy voice I've been hearing for a whole year. Edit: I actually use fish scripts and find them easier than bash scripts, scriptisto is pretty cool tho

[@AnthonyYouTube]

How am I supposed to enjoy this video? There's no catppuccin!

[@dreamsofcode]

Me and catppuccin have broken up 😭

[@uncenter_]

@@dreamsofcode :o whyyyy

[@christopherwood6514]

@@dreamsofcodewhat's the new theme?

[@dreamsofautonomy]

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

[@dreamsofcode]

@@christopherwood6514 Lol replied from my other channel!

[@christophercarillo4784]

Honestly, I can see this being useful for C/C++ codebases as an alternate to using using make files. Or CMake... I really hope that clang and gcc try and add scriptisto or something similar to their infrastructure!

[@AmirHosseinHonardust]

Does the LSP work though? If not, It might not be that ergonomics!

[@dreamsofcode]

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

[@AmirHosseinHonardust]

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

[@psmit29]

@dreamsofcode nice tmux config!! Is there a way we can this Tokyo night tmux config?

[@thiagoassisfernandes]

you have a face i feel betrayed...

[@dezly-macauley]

😮 Whoa. Haven't been online in a while so this is the first time I've seen this man's face. Ngl, it feels like Batman casually showing up to fight crime with no mask on. 😂

[@TehGettinq]

enjoyed the video but that tool is literally a shell script, only difference is it adds noise via the comment preprocessing thing. Just having a sh script that takes in the name of the script you want to run, to make it somewhat portable you just have a dir where the source code for the actual scripts are, that way it knows the path, based on the extension it runs cargo run or go run.. add the top level script in */bin and youre set.

[@dovh49]

V is set up really nice for this type of scripting. That's my go to for complex scripting.

[@twenty-fifth420]

Me, wanting to write scripts for fun and automation but don't wanna use bash. 😭 Me picking the most personal and practical language that has maybe 1/10th the size of 'popular choices' 😁 Bell ringer by the way. 🔔

[@dreamsofcode]

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

[@twenty-fifth420]

@@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.

[@twenty-fifth420]

@@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.

[@twenty-fifth420]

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

[@dreamsofcode]

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

[@bananaman9869]

Can’t wait to use my c shell to launch my interpreted vim to write my interpreted kernel to run on my interpreted version of qemu!

[@destiny_02]

for C and C++, cling interpreter has been there as long as clang.

[@SlackwareNVM]

I'd love to see some more bash content

[@Mempler]

I love to use Python for quick scripts. It generally performs better than bash while also being easier to use

[@dreamsofcode]

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.

[@Mempler]

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

[@boscovallejo-nagera6073]

@@Mempler Not just dependencies, but also python versions

[@05xpeter]

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

[@dmitriidemenev5258]

Doesn't poetry solve this problem?

[@Denis-wf4bl]

I was wondering a week ago how I could use compiled languages for scripting. Bash is good for a lot of use cases, but when it comes to error handling, I struggle a lot. In that case I like to use compiled languages. Thanks for this video. It is a nice inspiration for me 👍

[@dreamsofcode]

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!

[@xavhow]

I’m no expert but why not just run the binary to skip the compilation step?

[@martinseal1987]

Why are we making network requests in scripts?

[@SirJagerYT]

I actually prefer bash, for scripting. jq, sed, psql. created few scripts like: search bookmarks across browsers, chromium based and Firefox open or copy links. password manager using rbw, using rofi, bitwarden. And i need more control i simply use js.

[@japadkman]

I dont see a reason to use this, because when i write scripts its not just for myself but to share with coworkers, and them having to install scriptisto plus the language compiler just to run a script that could be done with bash and whatever other cli tool that unix provides just out of the box, its less of a hassle to deal with bashs weird syntax.

[@ashikurrahman2247]

I would love to see some bash content

[@tswdev]

To be fair, none of those languages beats Python for an alternative to bash. But bash is still king, it simply is way more integrated. I wish there was a language that was like Bash but without the wierd, impossible to remember, syntax.

[@dreamsofcode]

I think I may have found just the language 🤞

[@tswdev]

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