Bash in 100 Seconds

[@_sudipidus_]

It's called a SHELL as it hides the kernel Wow I never thought of it like that :))

[@Subuzgreatest]

Wonders of the English language.

[@BarraIhsan]

same lmao

[@farhanaditya2647]

Wow, thanks man. I never thought about it that way!

[@Joe3D]

In macOS is no longer bash, but zsh.

[@magicmulder]

Me neither. It’s like the German word for glove is literally “handshoe” but I never think of shoes when using it.

[@azatecas]

fireship is turning us into 10X developers without us even knowing it

[@Winnetou17]

It's ok, we'll just spend 90% of our time watching programming videos on KZbin, and no one will know then :D

[@gfjffdgjroedsfdkdslmerrelb4357]

i am looking for partner who want to learn bash through co opearation

[@BrandonCastillo-eo1or]

@@gfjffdgjroedsfdkdslmerrelb4357 How does this arrange works ? 🤔

[@mmmar7317]

I am currently -10x dev

[@GospodKrompir]

@@lolidkstudio Tru"e" programmers dont forget the "e" or your rely on autocomplete?

[@alexreade9229]

These 100-second videos are so underrated, no one else fully outlines a concept this well. I can see if it's worth learning before I invest my time. 🔥

[@dixztube]

So true. It got me into go and helped me with graphql back in the day.

[@gfjffdgjroedsfdkdslmerrelb4357]

i am looking for partner who want to learn bash through co opearation

[@heywrandom8924]

There is also the learn x in y minutes website for quickly learning syntax of programming languages

[@Lukyan]

So, the main take-away from this video is that the operating system is a squishy snail inside a shell?

[@____-gy5mq]

"bash the snail, crash the trail"

[@Flocksta]

Os is different type of shell i think

[@LupusMichaelis]

@@mr_madds No. And i won't dare to define what's actually an OS, as too many opinionated definition are out there in the wild fighting for nothing. A single binary, that's a first ^^ Even the monolithic Linux kernel isn't a single file.

[@GerhardusScheltema]

I always though the shell protects the squishy human from the awesome power of the kernel, allowing you to weild the awesome power of Linux without getting hurt by grabbing the sword at the wrong end.

[@martindjakovic7052]

If it’s windows, then yes.

[@thatsalot3577]

Bash literally taught me the true power of programming beyond console and libraries. Like it's the most useful language in automation, when you're just starting.

[@sophieedel6324]

lol

[@WebManager-y1h]

Bash itself a library

[@window.location]

add `set -e` at beginning to exit script if any command fails, `set -x` for printing commands that are being executed very help full while developing script.

[@childfs6865]

I had no idea. Thank you very much!

[@Pokefreak554]

You can also execute your script with bash -x file.sh instead of commenting and uncommenting your set -x while debugging :)

[@starpawsy]

can also use "set -v" fort verbose which simple echose the commands before executing them.

[@SeanSMST]

Thank you. Been learning to write bash scripts while doing my first today.

[@SeanSMST]

@@Pokefreak554 It's much easier to give x permission with chmod permanently than type bash -x each execution

[@SkyyySi]

Some thoughts: EDIT: Please stop telling me about `#!/bin/sh`. This video is specifically about bash and so is this comment. I am aware that posix sh... exists. If you want to write POSIX compliant scripts, use sh. If you want to write modern scripts, use BASH. Also: even if you use sh instead of bash, you may still be writing bash. The best way to test for that would be shellcheck. Oh and `/bin/sh` is not specified ny posix either, so you'll probably still want to use `#!/usr/bin/env sh`. - Please do not use `#!/bin/bash` or `#!/usr/bin/bash` as your shebeng. Instead use `#!/usr/bin/env bash`. This way, bash can be installed pretty much anywhere and it will still work. - Please always put double qoutes around variables unless you specifically need them unqouted (which you do when loop over an array using a for-loop for example). This will prevent unintended splitting of strings. Note that in bash single qoutes ('), double qoutes (") and backticks (`) all have a different meaning. Speaking of backticks: - Whenever you see a stackoverflow answer around processing a command's output, you will probably see someone using a command enclosed by backticks. This is deprecated and should not be used. Instead, you can use $(command). However, you should also double qoute that, so "$(command)". - Variables don't have to be all-caps. However, if you use them like " $VARsomething" where only VAR is the variable name, you may need to use curly brackets to signal bash where the variable starts and ends: "${VAR}something". Those can also be used for substitutions, which I recommend you just look up ;).

[@AlejandroLZuvic]

Great comment. Thanks!

[@____-gy5mq]

even better, use `#!/usr/bin/env -S bash` which can be generalized for any shell and any number of arguments before the script file.

[@Gregorius421]

Ah, substitutions are my wake-up coffee. Great advices.

[@slavko5666]

"#!/usr/bin/env" isn't standard on all systems though. For some reason there is no standard for shebengs.

[@tanmay______]

Bad idea, #!/usr/bin/env bash isn’t POSIX compliant and breaks compatibility on non-BASH systems. It’s better to use #!/bin/sh which is a symlink to the shell that is installed on the system.

[@nastygamer7929]

Fun fact: You can use $0 instead of $SHELL to get the actual name of the current shell, not just the path

[@maxrisku765]

not working for me 🤷

[@nastygamer7929]

@@maxrisku765 Really? What's the output of "echo $0"

[@alois6909]

That's because a bash program has it's process name located at $0 variable. Bash itself is a program running a "bash" process.

[@africayean1311]

@@maxrisku765 it doesn't work on ur pretty cmd

[@icarofilho6524]

doesnt work on Ubuntu

[@maniksingh92]

After 5 years of avoiding bash scripts, I was literally at the crossroads to learn it for some specific task. I wake up to find this video in my feed. This guy is a mindreader.

[@alii4334]

KZbin is the mind reader!

[@mohos_a]

No you're data is just being collected. Try some blockers

[@MaeLSTRoM1997]

@@mohos_a lol my thoughts exactly. google probably looked at his search history

[@iyxan23]

"Rust in 100 seconds" would be cool

[@janism94]

and WASM

[@Justin73791]

@@janism94 He did WASM, at least 100 seconds of it and he said he plans to do a longer video soon.

[@balu.92]

I've heard Rust is complicated. Curious to see how Fireship would do it.

[@tobiasdebruijn5240]

@@balu.92 it's not too bad honestly. I'd say the hardest is learning the borrow system and to work with the borrow checker

[@SamualN]

then zig

[@rafaelpernil]

Learning to make simple scripts with Bash makes using Linux way better imo. It allows to automate tasks without installing anything. It's not fully portable but, for what it's meant to do, it's great!

[@cicalinarrot]

That "bourne" -> "born again" evolution taught me how old the tradition of nerdy play on words is for programmers, even very important programmers. My favourite one is "Nero Burning ROM", it's just so perfectly layered.

[@TheOO23]

I like : gezerolee (french pun) and git !

[@fiandrhi]

Bash is possibly the most beautiful and manifoldly useful thing in computer science.

[@gregor3148]

Literally never wrote shell script and then it happened that I needed to put some code in background processing to the OS and started practicing how to write shell script. Once I got a hang of it, never went back from there. One of the most amazing ways to automate terminal commands and especially more useful to listen directly from your app.

[@-morrow]

I just hate the quirkiness and the different standards (POSIX, BASH, ZSH, etc).

[@xrafter]

​@@-morrow The only standard from those three is POSIX. Bash and zsh are shells. Also, why are you hating it, bash has --posix flag for that.

[@donaldteed35]

@@-morrow Then try MS Powershell - a standard that changes every year and requires modules to be loaded before many documented commands will work (and they'll never have a nice error like "blah blah not found"). I have bash scripts written over a decade ago that will work. The other weird part of PS is the | character sometimes behaves like a flag (|FL for full) and sometimes behaves like Linux pipe. PS is really non-intuitive and verbose and hinders everything you try to do (like defaulting to showing only the first few hundred results).

[@SebWayYT]

3 hours of uni classes in 100 seconds. I wish I would have found your channel back in 2019 when I started my CS degree

[@khandmo]

No shot that was 3 hours of uni you should’ve went to a different school

[@HenryTitor]

@@khandmoIt kind of is, most system programming introductory course will have a chapter for SHELL and terminal. It usually finish in 2-4 classes, which is about 3 hours

[@cnmy97727]

Ruduty de s

[@Gregorius421]

That was fast. Now to learn all the branching, variables, pattern matching and syntax intricacies it will take only a 100 weeks. Full-time.

[@alexradu1921]

Hello, what can I do with this Bash knowledge after? Can I be a sysadmin?

[@ehsanahmed5550]

@@alexradu1921 check out his videos for that: kzbin.info/door/vA_wgsX6eFAOXI8Rbg_WiQ

[@Gregorius421]

@@alexradu1921 This knowledge is enough to start getting familiar with Linux/Unix systems, to learn how to start, stop and configure programs and services and how to read and write the shell scripts that manage your system. These scripts coordinate the system, starting from boot (system init). It will take a few months of learning to become a sysadmin and years to master it.

[@aufkeinsten7883]

@@alexradu1921 It's an important tool that you should be somewhat familiar with, but there's more to being a sysadmin than this (I'm a regular dev, so I might be missing stuff, but networking, hardware, IT-security quickly come to mind)

[@MoonV29]

@@Gregorius421 I was like wth is bash because i had already been working in a linux/unix environment. Turns out i skipped quite a number of steps xD

[@Metruzanca]

Would love a longer bash tutorial as it's syntax can get pretty rough, especially with flags inside if statements which is something unique to bash

[@minnow1337]

Yea I was a little disappointed with the scope of this vid but at least it serves as an introduction to the technology for beginners

[@seerlite5256]

What do you mean with "flags inside if statements"?

[@manbillions8326]

It's an scripting language, it's not complicated

[@Metruzanca]

@@seerlite5256 I mean literally flags... inside if statements. Just as you would on the command line pass git commit the "-m" flag, in bash you can do stuff like if [[ -d dirName ]] which checks if dirName exists. Other flags I know of are -z & -n but theres probably more. (also if the double [[ ]] threw you for a loop, thats another odity of bash)

[@seerlite5256]

@@Metruzanca Oh so you mean flags for the `test` command. An if statement just runs a command and executes the blocks depeding on the return code: if mkdir dir; then echo "dir created"; else echo "dir exists"; fi It's the `test` command (AKA [, or the more sophisticated [[ in bash and zsh) that have different flags for what you're testing. You can actually use `test` without any if statement. Very useful for one-liners: [[ -f file.txt ]] && echo "File exists"

[@mavlonodev]

Fireship is literally turning the topics that I am scared of thinking It's too hard to easy labeled ones. Thanks Fireship!

[@basicnpcc]

Myself in college: Gosh, this Bash stuff is annoying to use. Good thing I just write Java for windows applications! Job: Hey, so we want you to code up some linux containers to deploy our Java application inside. You happen to know shell scripting?

[@BharadwajGiridhar]

So true

[@magicmulder]

Well I did try to use bash exclusively for my private projects but gave up once I needed YAML.

[@magicmulder]

@Andai Because it's too clumsy, even with tools like yq. Especially once you start nesting several levels deep.

[@TaskForce-wb7nq]

yeah most companies will want you to know how to use linux and shell, is important but one of the most boring things i have ever learned in life

[@tt-fx6nt]

Wow, best 100 seconds about bash. Please do more series like this, bash 100 seconds part 1, part 2 and so on in all 100 seconds video. Short, but very informative. Keep up the good job

[@mehdianisbrahmi9262]

wow I have been using bash for many years but this 100 seconds brought me so much new information I didn't know before, great job

[@Pedram-cy3wu]

I think & at the end of command just returns shell to you for entering new command and won't send execution to the background. For putting execution at background, we can use supervisorctl or "nohup &"

[@dankoller246]

I really love the animations of the topic logos in the beginning and end of the video. Nice details Jeff!

[@s1nistr433]

Using bash has completely changed the way I use a computer, there's so many things you can automate with it, like bulk zipping / unzipping files, installing all programs you use after setting up your computer, updating multiple things at once, bulk editing photos, setting up folder templates, backing up stuff to cloud storage. And when you use it with python scripts you can automate literally anything imaginable.

[@TheJamesconroy]

Hey variable names don't need to be all uppercase. By convention most variables set up by OS or programs are uppercase so it's usually a good idea not to make your variables uppercase. Doing that will prevent you from using and overwriting default's by accident.

[@ForeverZer0]

I have some personal conventions that I follow: Any variable that is exported and intended to be read elsewhere is all caps, and usually "configuration" variables at the top of a script. I do use lowercase for "local" variables that are used only within the script itself.

[@liveinthecity11211]

Bash has saved my butt so many times in development. Need to run a RESTful api several hundred times to test vulnerabilities? Bash is the answer.

[@palexer2505]

Golang/Rust in 100 Seconds would be great! And also: great video, as always.

[@ArivanAshstar]

Another amazing 100 seconds. Gives all the info u need quick and without padding or harsh opinions. Need to hear something again, just pause and go back :D

[@lawrencedoliveiro9104]

0:17 Command-line interpreters (CLIs) were not a revolutionary concept in 1971. After all, every interactive OS had them, and there were quite a few by that time. What was revolutionary was the idea that the CLI ran as just another ordinary process with no special privileges, rather than being built into the OS.

[@starpawsy]

Correct. But there were other revolutionany things about the concept. One of them was that it could be replaced by other products if you so wished.

[@JustinK0]

command-line interface

[@shellyreneegracia4030]

Secxy

[@turkym7md5]

your last tip about ending the command with & to run it in anothet thread saved me A TON! thanks a lot 🙏

[@xrafter]

You could see the result of command by running "jobs" .

[@shravanasati9631]

Golang in 100 seconds.

[@arkrait04]

Golang is marketing bullshit and an awful language made just so that graduates could copypaste CRUDs. The only good thing it has is a performant runtime.

[@albertbennett6290]

@@arkrait04 I will admit that it got worse after they introduced the module system

[@aArcziMetin2]

Mission Impossible

[@balu.92]

@@arkrait04 which language do you prefer for backend?

[@saadisave]

@@balu.92 Rust all the way. Go has a simple syntax, but you have to reinvent the wheel too often.

[@droidy347]

Bash is definitely the most useful thing ever created 🙏

[@PredaBoon]

Regarding the background command, make sure to put nohup either in the line itself or when running the script to make sure the process is not killed upon session closing. (usually the most affected is SSH logins since every shell is a seperate session.)

[@Paulo27]

nohup command & disown 😎 (disown prevents you from CTRL-Cing the command)

[@Imdeepakmp]

Always a fan of short and straight to the point vids of Fireship

[@michaelpoirier22]

I'd love to see a 100s video on a reasonably complex design pattern, like decorator or visitor

[@arisweedler4703]

I can't imagine explaining the visitor pattern in 100 seconds!! But I believe that someone who understands it better certainly could, and quote easily.

[@gfjffdgjroedsfdkdslmerrelb4357]

i am looking for partner who want to learn bash through co opearation

[@aquilazyy1125]

Fun fact, the “[“ symbol isn’t really part of the syntax but an alias of the “test” program. Both of which does exactly the same thing except that “[“ also checks for a closing “]”, which also isn’t part of the syntax but rather a parameter sent to the “[“ program.

[@leoniduvarov5236]

and that probably explains why you need a space after '['

[@jjlegend8819]

C++ in 100s. I think it deserves one given how much of the underlying web infrastructure is built with it.

[@try1994]

can segue into V8 nicely

[@taskforce_kerim]

Fully agree.

[@cbnewham535]

I wrote the O'Reilly book on Bash. It's nice to see such a nice concise video about Bash.

[@mallikarjunaswamyn483]

Fireship's 2 min videos are more like video cheatsheets. So cool 👌👍

[@seerlite5256]

Great video! Note however that by convention variables shouldn't be all caps unless they're environment variables.

[@stephan6530]

Or constants

[@WilliamAndrea]

Or special variables like $RANDOM

[@vanarpilipap302]

would you elaborate on what environment variables are briefly?

[@seerlite5256]

@@vanarpilipap302 Environment variables are variables that are shared to child processes. For example let's say I start a bash shell, set HELLO=1 and then I open python from the Bash shell. If it's a regular variable, Python won't know anything about it. However, if I mark it as an environment variable, Python will be able to access it via its API (os.environ). This is useful to pass settings to programs across many subprocesses. Some operating systems also let you configure "global" environment variables so that all shells start with those values by default.

[@framegrace1]

That's not the whole picture.... POSIX forces to any variable that needs to be exported has to be upper case or "_" . That includes what you call "environment variables" which really are bash RESERVED variables. Most old school shell programers like me always use uppercase because on those days, there was no syntax coloring, and in bash is really easy to mix commands, scripts and variables if all of them are lowercase. For those two reasons, you will see uppercase variables in bash scripts everywhere even from very respected sources.

[@maheshkumartangella5516]

I see the notification for fireship new video, I click. Simple as that

[@XxDarkCinisterxX]

Glad I'm not the only one

[@weiiswurst]

*fireship

[@necaton]

@@weiiswurst *Fireship

[@rezamostafid8810]

Aaaawesome....you pointed out all the salient features in 100 secs. Someone watching carefully could start writing a script. Of course that would be the start of the learning curve.

[@lorensims4846]

A couple of years ago macOS changed the default shell to zsh. Before Mac OS X 10.3 Panther the default shell was tcsh. Of course you can always change your shell by typing its name.

[@VincentJenks]

Right. Or, just execute the script with bash by prefixing with “bash” in the terminal.

[@vdynmx]

Holy. I never knew how much I needed to see this video. thank you

[@PrasangaBasnayake]

Wow that brought back memories of cs class. Aah the good old days 🤗 still thinking Id be able to make my own Linux distribution.

[@dripdrops3310]

This 2 minute video was enough to get me started righting some scripts.

[@alex283d]

Haskell in 100 seconds. Good luck, you're gonna need it!

[@gnatinator]

Fireship covering linux stuff = I like. I like.

[@ananttiwari1337]

awesome video. more in depth version soon?

[@arslantechlab]

This dude is God Gift for Developers😍

[@ark5458]

next video: quick overview of simple commandline apps like grep, cat, echo, sed, curl, awk, -ed-

[@xrafter]

Awk is a hole scripting language it isn't simple

[@exmax8781]

MAN, how the heck did you explain it that well in so little time? You're a fucking machine of great content

[@RhemaxosLord]

Any chance we get a golang in 100 seconds video?

[@andrepeixoto2947]

I like this 100-second video style better than the new ones. :)

[@JAVAxNANI]

Love you fireship ❤️❤️

[@damssiart9411]

Daaaaaaaamn!! the music used in the background made me eager to learn every single command in bash

[@lunkums]

incredibly easy to learn but takes a long time to master

[@droidcelestial]

Frankly I don't mind having long videos if this guy explains :)

[@YOUdudex]

Bash shell is love ❤️

[@MatthewTaylor86]

The Bourne Again Shell Shell

[@JustSomeRandomIdiot]

Perfect, that was everything I needed to know about bash to know whether or not it's worth investing any more time into learning it.

[@rudrapratapsinha8880]

Fireship posts video. I click.

[@MRJMXHD]

Comparing this Fireship video to the present ones, theres a lot of difference in cadence, delivery and speed. This video is more chill and laid back compared to his current videos.

[@Eyad_faramawy]

The person who watches your videos must know everything about computer😢

[@MichaelMilord]

you make it look so easy to write bash scripts lol. Love your content man, keep it up!

[@RawPeds]

One of the best things about bash is that it's immediately available on Linux. No matter what one installs on the top of the operative system, the bash is there.

[@xrafter]

Except it is a minimal install then only sh is available .

[@TheZoltan-42]

@@xrafter Or an embedded system.

[@hyrummoses5819]

I learned more about bash in this short video than in the first 4 lectures my professor gave.

[@gustavoviana5508]

"Lua in 100 seconds" would be nice. Both Awesome wm (one of the most used tiling window managers) and Neovim (the best text editor of course) are both written in lua.

[@skylinefx049]

Lua and Neovim are trash

[@007arek]

I've learnt Lua recently and it's such a fun to use language. I don't know why nobody uses it for scripting instead of bash.

[@gustavoviana5508]

@@skylinefx049 w w w w w w w who asked you

[@manbillions8326]

@@007arek Because it's not zero indexed

[@007arek]

@@manbillions8326 In Lua it makes sense with associative arrays. AWK does something similar, white spaces are stored in 0 index.

[@jamesbank833]

I just started learning bash a few weeks ago, this is a great intro!

[@creeperkafasi]

Windows Users: **Confused screaming**

[@abhaythakur8572]

you should also create long videos as well, your content is the best

[@randomrobin6104]

Great video as usual ! Kafka and MQ in general in 100s would be great 😁

[@linixo7485]

Learned more than in a 3 Hour Tutorial! Keep it up!

[@alexzander__6334]

1:09; these sources are from zsh prompt themes, NOT bash.

[@shahriarahmed4316]

don't mind but your tutorials are like showoff of an expert , also i learned a lot from your videos , thanks

[@ranaakhil]

JAM Stack in 100 sec.

[@asafnisan]

This was amazing. Thanks. Love and respect from Istanbul.

[@JayJames]

1:21 I like how you say "shebang"

[@Koyi_supremacist]

Bestest coding playlist, keep going men👍

[@DenisDuvauchelledev]

I like it when you do “something in 100s” but then go longer after to go more into details.

[@gaius100bc]

Wow, these videos are all just.. wow After each one I feel I got at least 10 times smarter than I was mere 100 seconds ago. Fireship achieved mastery in greatest art of all arts - education.

[@antonioquintero-felizzola5334]

Quick correction, Linux is NOT based on Unix. It's a Unix-like operating systems based on the Linux kernel.

[@drkskwlkr]

I hit the Like button because there wasn't a Love button. Great summary and beautiful visualization! ❤️

[@armchair_expert]

I have been developing software for over a decade and I still hate bash. It would be awesomeness if you wanted to do a longer bash video, that deals with all the counter intuitive intricasies in a way that you can almost make sense of it. Just praying 😃

[@ethanoppenheim2884]

Answered all my questions in 100 seconds. Thanks

[@mirashif]

Bash beyond 100 seconds.

[@yajatvishwakk6744]

We has a Unix programming class in our college, it lasted 3 months. This is all that was taught.

[@IAmLesleh]

The default shell on macOS is now zsh. It switched away from Bash when Bash switched its license to GPL v3.

[@nevoyu]

I learned more about bash in 100 seconds than I have in 15 years as a full time linux user (work and home)

[@mdanish18439]

Comparing Shell with JS, which one is hard to learn? rightnow im learning linux but never touched the scripting side. Thankss

[@Afsafs123]

Waiting for The Friendly Interactive Shell (FISH) in 100 seconds now

[@Zephyrus0]

Not POSIX

[@Afsafs123]

@@Zephyrus0 for a personal machine, I truly don't care about POSIX compliance.

[@Zephyrus0]

Makes sense, but you would need a POSIX shell if you are using someone's scripts or vice versa

[@shr1han]

1:30 It is to be noted that there shouldn't be any spaces between the variable name, the equal sign, and the assignment. Otherwise, bash would think GREET is some command and = and "Howdy Partner" are it's arguments! Weird, but it is what it is.

[@DerChrilleAusBln]

The default shell on macOS is now zsh not bash anymore

[@ananttiwari1337]

He addresses that in the video, he mentions "pre-catalina" in the graphic

[@Fireship]

That's why noted it with "pre-catalina".

[@DerChrilleAusBln]

Ah my bad sorry

[@AlejandroLZuvic]

@@Fireship I have a question: if the shebang correctly references Bash wouldn’t the terminal invoke Bash to run the script? I know ZSH is the default shell but Bash is included along ZSH as well. Also, it’d be great to have a “ZSH in 100 seconds” to know the biggest differences and/or a “beyond 100 seconds”. That’d be really awesome, I always wanted to jump on Bash scripting but it seems so daunting. Thanks for the hard work!

[@ananttiwari1337]

@@AlejandroLZuvic "I have a question: if the shebang correctly references Bash wouldn’t the terminal invoke Bash to run the script? I know ZSH is the default shell but Bash is included along ZSH as well." Yeah I'd assume so

[@JohnVance]

This was really good, subscribed!

[@Darkev77]

"Command Prompt" in 100 seconds please

[@niksatan]

dude thanks, this video helped me a lot, 100s is more than enough!

[@devhypercoder2522]

Please do linux distros in 100 seconds. Debian: Outdated af but stable Ubuntu: slightly less outdated, also newbie friendly. Manjaro: meh customised arch Arch: bleeding edge, stable (if you know what you are doing) Gentoo: compile everything (use binary if impatient) Lfs: true chad

[@techgregory5253]

Debian is not outdated, it's just not user friendly and not feature rich

[@kurshadqaya1684]

He has already done that. kzbin.info/www/bejne/iZnGg2eQm8hpetk

[@techgregory5253]

For beginners I recommend: 1) Linux Mint Cinnamon. If it won't work properly try installing proprietary drivers. If it still doesn't work then try 2) Pop! Os which has rich hardware support. If for some reason it won't work properly or you just don't like the UI or you don't want to customize the default Gnome UI then your next choice might be 3) Manjaro. But keep in mind that Manjaro is Arch based and not that stable as Mint/Pop! OS as it get the latest (not super well tested) apps and software. Manjaro has Gnome, KDE editions (desktop environments) and some others. Gnome is solid, stable (in terms of UI) and well polished while KDE is a bit lighter (in terms of RAM consumption) and very well castomizable. These are 3 the best Linux distros for me. Fedora is also great but not for beginners.

[@techgregory5253]

Also there are other independent (not Arch or Debian based) distros to be mentioned in video: OpenSuse, Gentoo, Void Linux, CentOS, Solus

[@Akimb321]

The syntax is really funky. Unix people like to state that Windows is not programmer friendly, but compare the syntax of bash and PowerShell...

[@othman_]

Please explain data science, machine learning or AI in 100 Seconds

[@andreic6250]

wow amazing, make a 1000 seconds one - and you will cover most of it loved it thank you

[@heheheha529]

This is misinformative, the syntax you showed is available in any POSIX compliant shell, such as dash, zsh and others. The first line should be #!/bin/sh because it will be executed in dash which is a way faster shell than bash. You should use #!/bin/bash only if your script contains syntax that is only available in bash, which can usually be avoided

[@ThePowerRanger]

The intro animation was fire!!🔥