Rust enthusiast here. These are some other amazing rust tools: - zoxide (smart replacement for cd) - hexyl (nice hex viewer) - nomino (batch renaming) - sd (intuitive string find+replace tool) - du-dust (disk usage analyzer) - eva (cmd calculator replacement for bc) and there are many more :D
Yeah, I already did that @@flyingsquirrel3271 I realized I didn't ever thank you for the tools you pointed out. It has been a great time since I started using zoxide and eva. I appreciate it man!
The biggest reason for ripgrip (rg) wasn't mentioned: speed. When it comes to recursive searches, rg absolutely destroys stock grep. It's way, way faster. It's also clever: that pretty output that it does to make it more human readable only occurs when it knows the output is the terminal. If you pipe the rg results to anything else, it knows that and switches to the more typical line-by-line response.
As a professional programmer I can tell you, is not a meme, is just a really cool language that has a very innovative memory management that offers the safety of a garbage collected language, without the garbage collection or any overhead/bloat of runtime, because it uses a memory model of 'ownership' and borrowing with a powerful type system that C can only dream of.
@@aedd3307 ok. But in practice the experience is the less command. So in reality it replaces less more than cat (at least by default idk if theres any flags)
@@aedd3307 and that's exactly what a 'cat' replacement must not do. 'cat' comes from 'conCATenate'. The intended usage of 'cat' is to concatenate multiple files, as in '$ cat file1.txt file2.txt >> file1-2.txt'. Thus 'cat' must not mess with the input stream unless you explicitly tell it to do so. If you replace standard gnu utils the system relies on with tools behaving differently (like eg 'alias cat='bat') things will break.
You forget alacritty which is the terminal you are using in this video. For Rust, people are switching to it,because it is a very replacement to C++ that has similar performance while handling memory in a better way and being memory safe
I am a Sr Software Engineer who does know Rust. Rust is a "immutability first" language. Often times the reasons vulnerabilities in code occur is due almost exclusively to mutable data in memory that's getting modified in real-time by other software trying to take advantage of the memory exploits. Rust makes mitigating this a first-class citizen. Which means, if immutability principles are followed, the amount of vulnerabilities will naturally fewer and, when they do occur, much less likely to have downstream effects, while being more easily maintained. Rust as an amazing system-level language. It is a C-level language. Other languages based on Rust are coming down the line at some point. NodeJS linked-libraries are being written in Rust as well as Web Asslembly. Web Assembly is a compile target of Rust for web applications. Rust has a TON to offer the software community.
immutable variables in rust only guarantee compile-time immutability. They can be modified if the program is hacked. On linux you need to mmap a memory region and use mprotect to prevent the data from being modified at runtime.
@@apestogetherstrong341 I get what you meant but that *can* actually happen in both Rust, C, and other languages. It's called "const promotion". Basically, when the compiler recognizes that it's safe to perform the calculation at compile time and store the result in the compiled binary as an optimization even though you didn't use explicitly use `const`. That said, Rust *does* help to give the compiler backend more freedom to do stuff like that by making stronger promises about how things will behave. (And, as such, it'd also be more amenable than C or C++ to automatic insertion of calls like mprotect.)
@@ssokolow well, const promotion can't happen with something like "let x = arg_1 + 2", in that case it's just incrementing the stack pointer and moving to it. But yeah, i get what you meant too
@@Muttisuri yes you can use cargo but tbh using the package manager is better because updating the packages would be much easier as you dont have to keep doing cargo install --force every time theres a new update for exa
I struggle to keep up with all the new CLI tools in the ecosystem... so it's great to just watch a roundup video like this one. Thanks and looking forward to more roundups!
Dude, I absolutely love your channel. I've been an emacs user for seven years and switched to doom about a year ago before finding your channel. I always learn something useful from your channel and this vid is no exception.
Go and Rust are popular modern systems programming languages for a reason. Built in build systems, package management, and testing suites lead to building robust fast reliable software very quickly. Just look at how fast the Pop!Os team can pump out really good systems level software with some of the best runtime safety in the game. Go routines provide a revolutionary way to implement concurrency. So many benefits behind these languages. They also lack all the "history" and backwards compatibility bloat issues that languages like C++ have. Referring to these languages as "memes" merely shows a drastic misunderstanding of what they accomplish.
They aren't trying to rewrite windows but they are experimenting,how well Rust could fit into their ecosystem. medium.com/the-innovation/how-microsoft-is-adopting-rust-e0f8816566ba
> I don't see why anyone wouldn't just replace `cat` Because it works just fine, and you really shouldn't be using it for reading files at the terminal (use `less`). Rust's advantage over C is its memory safety. `cat` is already memory safe. Thus as a user, there is no advantage to me switching.
@@randaldavis8976 It depends on the man page. For example, Linux programmer's manual have some nice usage examples. Anyway, I think you might make use of `tldr` command
@@randaldavis8976 pipe it through bat. It improves it :). Then in fish, make the bat an abbr for man, and there you go, it will always do this for you no extra typing
A year and a half has passed since this vid posted.Amazing stuff going on in Rust.Pkg's,like alacritty DT did showed us what cpu accelleration accomplishes.Rust doesn't do null reference (Tony Hoare conjured that up in 1965.Stated in public forum 2009 that null reference was $billion mistake.)Valid Rust doesn't,anyways but one can try unsafe Rust to get through compilation.Hazard pointers need to be dealt with correctly,though,or panic/crash at run time.Rust doesn't do garbage collection. 100% thread safety.Suscinct error handling.Zero cost abstractions.Rust compiler expects all but absolute perfection or no compilation.Even details minor 'errors' at run time,if any. ie #[error(unused-variable)] concider using '_' .The detail in Rust compiler info is something else. Even most experienced computer science phd's get stumped here and there in Rust.This language is a whole new ball game even though it's C++11 and C++20 at core. Alien/Greek to those familiar with earlier computer languages.Cat's out of the bag now and those who bawked before now realize they better get on board or get left behind.Rust stuff coming faster than tutorial vid producers can deep dive into it. async/await concurrency is revolutionary.It looks like Rust is going to blow the lid off everything ever written code before.
Ignoring the discussion c/c++ vs rust, the problem I have with these rewrites is that they often change the default behavior and interface. There most probably is a reason why tools behave the way they do, even if you as a user don't understand or know it. cat, ls, find, ... are all POSIX standard utilities the system and a lot of software relies on that you simply cannot mess with. You want to reimplement gnu or standard utils? Fine, but retain default behavior and the interface. Otherwise, do not advertise them as replacements, bc they are not. They are alternatives, but not replacements.
@@bigpod replacements have exactly the same behavior and are completely interchangeable. Not the case with most of these rewrites. It's like changing APIs or interfaces. If they do not behave exactly the same, they are not interchangeable and thus not replacements. Also you should care about standards like POSIX because they guarantee interoperability and portability. But then again, if people do not understand the crucial importance of stable APIs and interfaces, and why there have to be reliant contracts for IPC, then they shouldn't program essential tools or services in the first place. Changing well-known, reliant and expected behavior, just for the sake of being different and promoting one self's ego (I know better, I do it my way), will break systems and make maintaining interoperability between processes a nightmare.
@@bigpod try the following then: $ sudo cp -f ~/.cargo/bin/bat $(command -v cat) $ sudo mkinitcpio # on arch, or update-initramfs on debian, check your distro $ sudo reboot With my understanding of replacement, this should work flawlessly, but then again, my understanding could quite possibly be flawed. Chances are, your system won't even boot anymore, because 'cat' is an essential binary used in the initial ramdisk to boot practically all unixoid OSes, which is possible thanks to standardization like POSIX. But since you do not care about standards, interoperability and portability, having to repair constantly breaking and non-functioning systems is probably not a problem for you anyways.
the difference is that C is a programming language with the most basic features from the 1960s these features allow you describe low level stuff C is basically a template language for good programming patterns in ASM but this comes without safety and is prone to produce all sorts of damage like segfaults Rust is a programming language with sophisticated features from different languages including Programming Language Theory (research) including the experience of the last 30 years in the industry and lessons learned in C++ also allows you to describe low level stuff its memory model protects you from segfaults without producing any runtime dependency (due to that ivory tower research that hackers tend to despise) basically C is garage amateur carpentry while Rust is space tech engineering.
You should check out nushell. It's a shell written in Rust. It's now at minimum viable product status. I doubt you'll use it as your main shell any time soon, but you may find the general concept to be interesting. Like fish it isn't aiming to be POSIX compliant, but is instead trying to evolve the shell as we know it.
@@IcarianHeights Right now? Probably. Long term, who knows. That said, nushell isn't trying to be a PS clone, it's just borrowing some of PS's concepts along with others (such as the functional programming paradigm).
it's not just a "less"-feel for e. g. bat command (and I would assume probably the process listing one, too), it literally just pipes into "less". AFAIR, the choice of pager is also configurable; might have some kind of environment variable.
The only true con of Rust is that Gentoo user will wait more for their software to compile. Rust has a lot of pros (security, speed, compiler errors, memory management, ...) even though purists will always prefer C and Go may be seen as simpler.
Nobody who really prefers C should be called a purist. It's about the most impure language one could create. (Spoken as someone who's been programming C since the 80s....)
Assuming you aren't trolling here there's a clear difference between Rust, a programming language and Firefox, Thunderbird, etc which are internet programs. Rust is a programming language, it is harder to censor and almost conpletely pointless to do so anyways because of the abundance of other programming languages which aren't censored. Mozilla's other software like their browser and their email client are much easier to censor and there is a motivation to do so.
The reason your .bashrc didn't show up in fd is because fd ignores hidden files by default. Also fun fact - bat uses less under the hood (and i'll guess that procs does as well)
Sorry, but judging by the output of bat, it's not a replacement of cat, but for something like less or more. Because when using cat, you only expect the file content to show up on stdout. That's necessary for piping as well.
Can I ask why you have the super hardcore mixer / sound setup in the background? - you could master Bon Jovi with all that - its not podcast / youtube stuff :)
I haven't programmed anything serious on Rust, but as far as I have seen about the language, it seems to be a modern and better version of C++, I have programmed on C++ since before C++11 was a thing and by today's standard C++ has became a very bizarre language. For example on C++ is a best practice to mark every variable as «const» or «constexpr» unless you need it to change while on Rust variables are «const» by default and you only need to mark them as «mut» when you need it. Some people have said that “Rust is not as efficient as C++” by comparing the ASM output of same codes, but that is not true, the compiler might not be as efficient, but IMHO the language is as efficient as C++.
@@ekremdincel1505 Sorry I can't find the video where I found the original source, but I remember the video comparing the output of the same program using godbolt.org/
alias bat="cat" is bad advice, since you couldn't pipe the contents of a file in an interactive shell using cat anymore. Better use alias cat="bat -Pp" instead.
@@basedfacistman The whole point of having a compiler with same programming language will then be ignored. There is no point of rewriting something to reproduce same output (grown compilers such as gcc will take years to fully replicate in other language if not giving up before). It's like you are telling someone to rewrite something just because rust is superior, in the end will it be worth it?
@Nate Higgers That's one thing I hate about rust binaries. I remember one day when I used a musl static compilation to get a >60 mb executable for an ftp client, where In c++ I managed to get 4-5 mb
Rust is basically C++ with an extremely strict compiler with far improved error messaging for developers. Rust is focused on avoiding bad security practices. You cannot compile code that has glaring security problems. It will stop and force you to fix your code and it Is pretty good about giving you a meaningful error message for the compile failure. Rust is far more opinionated and security focused than C++ which allows a developer to do whatever they want without much complaint, providing it compiles. Rust will stop someone from compiling bad code. Rust won't remove all security issues but it covers the big ones that are most common among most security exploits. This is why there is so much talk about using Rust for systems programming such as an OS kernel. Linux is looking to allow device drivers to be written in Rust. But that isn't the only reason to choose Rust for any development project. It's a very nice language and that compiler still gives you much better feedback when a compile fails. Lots of people have been dipping their toes into Rust and that is why there are so many nifty Rust programs. Rust programs can be highly performant.
bat seems like more of a less replacement than a cat replacement, unless it behaves differently in scripting contexts. The thing I want out of any cat program is 1) it outputs all the characters from a file in order, and 2) it concatenates the things I give it. The formatting makes it kinda useless as a cat replacement.
Cat is one of the few things in GNU Coreutils that doesn’t have any colorization in its output. Even ls is starting to use colorization by default in most cases. Disabling the colorization is pretty easy. There are a few fairly standard ways of testing if a file descriptor is connected to a terminal.
I ve got an off topic question, as you are using the ergodox. There is something like the zsa moonlander have you ever heard of it if yes is it likely that you would give it a try if the one you currently got for example broke? Unfortunately there aren't many user videos and like reviews so that there would be more than just first impressions...
There are quite a decent number of reviews now. One guy even specializes in it. Just search for ergodox vs moonlander. A british guy did a fantastic review of both. There are some major differences, and I mean really significant to consider. I would tend to say moonlander si better, but ergodox also has ome points going for it. It depends what you want. I ordered my moonlander a week ago. Still 1 month to go till I receive it. Major differences I found: moonlander is more compact; better for travel. The thumb area swivels, this is more ergonomic and also allows for adjustment for smaller/bigger hands. Thumb area has better key redesign. Moonlander has RGB on every single key; not so on ergodox. Lot of keys do not have RGB. RGB is thicker, more robust and also since thumb area does not pivot, it has 1 less point of breakage in the hinges. In fact the reviewer in the youtube video I mentioned - his hinge on the thumb pad broke. Could have been a defect though. Moonlander uses type c cable (not that big deal though). Exterior row on each side has keys that are less wide on the moonlander, bringing the center point where you press closer to your finger, which could be important. These are some major highlights. Cost is the same. It was here, on DT video I learned of the ergodox and subsequently bought the moonlander! Super excited.
Great stuff. I always seem to get something good from every video. I don't have a linux machine right now, but I have been putting all of this knowledge to use in my WSL/openSUSE setup. Granted, not everything wants to run on Wayland, but most things do it just fine. A quick edit of my alias list and I can now see folders and files by color and sorted. Before, I couldn't tell a folder from a file. Awesome. For FD, I set an alias for "find" to search where I am and I set "search" to search from the / directory. Sweet.
Pretty sure people are switching to rust because it removes the performance issues of C++. As well, its syntax forces you to write clean code. Don't know the C family myself, but would definitely choose rust to learn if I were to pick it up.
Not really. The performance of C++ is not an issue. C++ is very performant. It's really just the modern syntax and concepts that lets you write safer code with not that much effort, without sacrificing performance.
In my experience Rust and C++ perform about the same (very close to C). I find Rust far more pleasant to work in though. I tend to write code faster in Rust, in part because it doesn't need as much boilerplate as C++. I spend less time debugging Rust code too.
And unlike in C and C++ getting 3rd party dependencies is not a realm of incomprehensible suffering. You just declare what version of the package you want to use and it works.
@@whenimnotaround If that is the case, why are still a lot of video games written in C, precisely for the reasons because it gives them more performance?
The linux kernel and most of the linux programs used to be written in C which is a very old language and even for those with experience it can be hard to write code in C, rust is a new programming language which can replace C because it's also low level, so it's very fast (not faster than C but close) and it has some features that make it easier to code in.
Recent benchmarks have shown that Rust can be faster than C. However, I don't think of Rust as a C replacement but an addition to systems programming. There will always be scenarios where it'll be preferable to use C/C++ in systems programming. Rust allows you to write low level code in a precise, short and abstract way - that is brilliant. But it also has very strict rules and sometimes doesn't let you do "your way of programming". Nevertheless, I do most of my programming in Rust. I just don't think of it as a replacement
@@lieywe3438 How can it be faster than C? Is it a compiler issue (poor optimisations by C compilers), or is it the langage itself? It seems to me that C is closer to machine code than Rust. So I don't get how Rust could be faster.
@@brinckau Rust, as a abstract language, has more optimization opportunities than C, the abstract language. It is about language semantics. And C is not more close to the hardware than Rust, they are same.
@@ekremdincel1505 Assembly is not an abstract language, is converted to machine code without any optimization, and yet cannot be beaten in terms of speed (because in the end, everything is machine code, so writing machine code directly, or assembly code, makes it possible to do exactly the same as a C or Rust program would do). Provided you're good enough to write excellent code, of course. So I'm not convinced by your argument about optimization opportunities. I also believe that C is closer to machine code than Rust, because Rust has more abstractions than C. Otherwise, Rust would not have more optimization opportunities than C.
@@brinckau Every language is abstract. I mean the formal definition of the language regardless of current implementations. I didn't even say anything about assembly in my previous post. You can write inline assembly in Rust. Rust's abstractions are zero cost. And having useful abstractions not necessarily prevents you from having tools for writing low level code in your language. Rust have both safe references and unsafe raw pointers, for example. "So I'm not convinced by your argument about optimization opportunities." An example about language semantics: Rust inserts C's equivalent of "restrict" keyword everywhere, thanks to it's borrow checker, and this gives the more optimization opportunities. People use the "restrict" keyword in C so rarely. Not everything is theoretical.
People love rust because it can be written at a pretty high level but without the disadvantages of other similar languages like go because it's not a garbage-collected making it wicked fast.
there is *git-delta* which is a better diff, you can configure it with git and then see the diff in color, custom color schemes, and even side by side diff, with numbered lines on each side. It goes great with *bat*.
Not a programmer by trade, but until now, I come to love every Rust program I ever used. Fast, efficient, easy to use. _fd_ is such a breeze compared to the standard _find_ command. _exa_ has won my _ls_ alias. I'm still looking for a window manager written in Rust. Will you dive into that, DT?
@@itsamcb Not really. Windows 10 was one of the most important reasons for me to switch to Linux. 😂 Seriously, is anything about Windows actually written in Rust? I thought it was all C++?
@@marioschroers7318 what he is trying to say is that if you love bloated stuff over very efficient and already working standar tools the you should as well go ahead and get windows
@@JosueRodriguez08 The things is that, for instance, ripgrep and fd are much more efficient than their standard counterparts (see their benchmarks on their github pages). All of that with better memory guarantees. Go ahead and go use "more" instead of "less", why not.
bat vs cat - is If "bat file | grep 22" will get lines with 22 or line 22 too? How much slower is it? same question with all of them - old gnu utils can be chained - can these? Will they break old scripts?
Rust language would be my top choice for a programming language to be stranded on a desert island with a laptop and solar powered battery recharger - if could have only one language choice. It's intrinsically versatile enough to be applied to about any programming domain - with Web Assembly support, could even be used to write programs that run in the browser. And presumably being stranded on said island, would have plenty of time to master its borrow checker and annotations - and the cool kids stuff like pattern matching and other functional programming features. And finally get around to learning how to write macros in its powerful macro sub-language.
haha it's COVID time, we're all stuck on an island...your wish came true...get cracking....as for me, I live offgrid in the mountains in Canada, so, pretty much the scenario you already describe....
You'd have plenty of time to program, on this desert island, for about a week, until you became so weak from lack of food that you couldn't type any more. :-(
I liked most of this programs but I'm not switching to most of them because if you run for example cat the file stays in the terminal but with bat when I quit it isn't above(it don't stay in terminal) same with Procs
bat uses your $PAGER (less by default) to display its contents when in an interactive shell. This can be bypassed with the -P option, or configured to use a different one, or none.
@@bigpod I am not worried about DT and I appreciate its content even though I can have differing opinions. His audience should be aware that exa is not the same software as ls; both programs perform differently and both programs take different arguments. I don't think it's a good practice to let pretend that an application is what it isn't. That being said someone can still bypass aliases using quotes or backslash. Knowing this, people are free to do as they wish.
colorls is a ruby port of ls. I think colorls is better then exa because it has all of exa color stuff but it has file icons and has the date of the file that changes in tint based off date
Maybe lsd? (lib.rs/crates/lsd) I wouldn't want to have to wait for an ls replacement to wait for Ruby or Python or whatever else to seek around, gathering its files, if I'm still on an SSD-less machine and they're not already in the disk cache.
I can't say about all of them, but ripgrep is specifically designed to be faster than all competitors (there's a whole blog post linked from the README going into great detail on it) and, while piping things through pygmentize is known to be a bit sluggish, bat uses a syntax highlighting library named syntect that's specifically designed to be lightning fast.
A big part of it is that they want to write Rust code but they don't have any original ideas so they pick an existing tool that they think they might be able to enhance.
I would probably start using these all right away, but much of the work I do is on company servers into which I cannot install what ever I fancy :/ So I think that except for Alacritty and Fish shell, I have to stick with the old ones for now so I don't remember which commands are available on which computers... Thanks for the list though, it is nice to see that more and more Rust programs like `bottom` to replace `htop` are coming!
Often, it's preferable to stick with commands that are standard/default to most machines. Getting efficient/proficient with those "standard" commands offers much higher "return on investment" because that skill is more "portable". So while all these tools are cool, it's not cool enough for me to invest on them and abandon the more widely available standard commands.
I tend to agree with sticking with the POSIX standard tools but would point out that these rust tools are statically compiled binaries that you can copy around via scp/ssh and run them arbitrarily without even needing to install them into a standard $PATH. Cant imagine doing this for a prog written in python or node/typescript however.
DT you amaze me..... you are very good at this.... I am learning at such a high pace because of this...... if you enjoy doing this channel please keep going😎
You have to feed the cults! You can have a bad design written in the fastest language and it could still run slower than a good design written in python
@@LabiaLicker There are a lot of reasons that statement is an oversimplification, but an /etc/sudoers parsing bug isn't one of them. Parsers are the first Firefox components Mozilla started rewriting in Rust because it's so well-suited to writing memory-safe parsers. Sure, anyone can abuse `unsafe` and be an idiot, but writing a parser typically isn't the place where people think it's necessary and a good idea.
Let it mature first and we'll see. It's pretty obvious to everyone who is not part of the rust cult so far that there will be many issues. No one is arguing the language is good. The language also has a lot of future. It's just at this moment it's far from being the thing people claim it is and it is about to be.
The presets are nice but the power of GNU tools is not their single unit efficiency but their composability. it's much hard to compose things that have tons of post-processed output because the post-processing adds things that aren't usually there Arguable most people don't use GNU tools like that or know GNU find can exec on a file. Granted all of this rust application absolutely do that its just it is less intentional here and they are not doing them now
There always have been alternatives to GNU utils. And that's for the better, GNU utils are often bloated… which isn't quite improved with these Rust alternatives.
2:08 Why do youtubers use “clear”? Is there a benefit to it instead of using Ctrl+l? I’m genuinely curious. ‘Cause I’m so confused that you use a window tiling manager to be “productive”, saving every keystrokes as possible, not using a mouse, but still types “clear” in the terminal, which I think is commonly used. I’m not being rude really. I’m noob in Linux so I most probably am missing something.
I didn't know that Ctrl-L is not default for all terminals/shell. Good to know. 'Cause every distro and/or DE I tried with the built-in terminal, it just works. I'm also using vim keybinding in the shell (zsh) and Ctrl-L still works. I didn't rebind it or anything. Also, I understand if it's really for the youtube video showing what he's doing for the viewers. If that's the case, then that's totally a valid reason.
Dt used to do retail full time and youtube as a hobby but now he does exclusively youtube. He has also never been a programmer by trade he's said it a lot.
Rust enthusiast here. These are some other amazing rust tools:
- zoxide (smart replacement for cd)
- hexyl (nice hex viewer)
- nomino (batch renaming)
- sd (intuitive string find+replace tool)
- du-dust (disk usage analyzer)
- eva (cmd calculator replacement for bc)
and there are many more :D
lmao what was that? Are these bots?
@@paulosantana9607 Yes they certainly are. I saw the exact same comments under other videos as well. Super annoying. I hope nobody falls for this BS.
It's spam. I recommend you report these as soon as you see them.
Yeah, I already did that
@@flyingsquirrel3271 I realized I didn't ever thank you for the tools you pointed out. It has been a great time since I started using zoxide and eva. I appreciate it man!
Ytop is a nice alternative for top/htop as well
The biggest reason for ripgrip (rg) wasn't mentioned: speed. When it comes to recursive searches, rg absolutely destroys stock grep. It's way, way faster. It's also clever: that pretty output that it does to make it more human readable only occurs when it knows the output is the terminal. If you pipe the rg results to anything else, it knows that and switches to the more typical line-by-line response.
Same goes for bat when piping it to another program
How does it implement that differentiation? Does the stdout printing module have some option for that
As a professional programmer I can tell you, is not a meme, is just a really cool language that has a very innovative memory management that offers the safety of a garbage collected language, without the garbage collection or any overhead/bloat of runtime, because it uses a memory model of 'ownership' and borrowing with a powerful type system that C can only dream of.
Yeah RAII didn't exist before Rust. Of course C++ is the same as C. Of course it's not a meme, with all zealots telling to rewrite programs in Rust.
@@SbF6Hwell, actually rust memory system is not based on RAII
@@user-sn9dy5sq1q Yeah it is based around furry magic.
@@SbF6H No,, just on type system. Why so arrogant lol
@@user-sn9dy5sq1q What? Furry magic is omnipresent.
Bat really isnt a cat replacement it's more of a less/more replacement
True.
not true though, bat justs highlights syntax and adds line numbers, then sends its output to less
@@aedd3307 ok. But in practice the experience is the less command. So in reality it replaces less more than cat (at least by default idk if theres any flags)
can do the same with cat -n .zshrc | less
@@aedd3307 and that's exactly what a 'cat' replacement must not do. 'cat' comes from 'conCATenate'. The intended usage of 'cat' is to concatenate multiple files, as in '$ cat file1.txt file2.txt >> file1-2.txt'. Thus 'cat' must not mess with the input stream unless you explicitly tell it to do so. If you replace standard gnu utils the system relies on with tools behaving differently (like eg 'alias cat='bat') things will break.
I think using Rust is the new "i use arch btw"
Then there’s me, installing exa on macOS (I’m not joking, it’s available)
@@ultradude5410 yeah most of us know about homebrew or macports
bat works on windows :)
@@YoloMonstaaa Man bat is just amazing, i have to admit
@William Berry no it isn't
Rewrite every GNU tool in Rust so you can say "I use Rust/Linux"
Rewrite Linux in Rust and call it Rusty Linux
Goals
@@Handskemager no.. why would it? as long as if it's FOSS..
btw
@@Handskemager considering they are all clones of UNIX commands, no
Bat should have beed called "rat", because r is for rust
brat
Pin this comment already 😂😂
Ah but cat gets to eat rat. At least bat could get away
But bats are flying rats (check their faces in google image)
Thank god alias exists
You forget alacritty which is the terminal you are using in this video.
For Rust, people are switching to it,because it is a very replacement to C++ that has similar performance while handling memory in a better way and being memory safe
Yes, also.....broot. Another Rust program that I have talked about on video.
haha, exactly what I was commenting!
Actually rust goes lower than c++
On c level
@@Reliktish Nope, Rust has vectors,HashMaps(python dict),VecDeques,BTreeMaps, also you rarely interact with pointers directly ,like modern C++.
@@siddharthupadhyay6347 yet is it designed to be used in the fields that are exclusive to C, like embedded systems
The major thing with ripgrep for me is the performance. You can ripgrep through big projects considerably faster than with grep.
I am a Sr Software Engineer who does know Rust. Rust is a "immutability first" language. Often times the reasons vulnerabilities in code occur is due almost exclusively to mutable data in memory that's getting modified in real-time by other software trying to take advantage of the memory exploits. Rust makes mitigating this a first-class citizen. Which means, if immutability principles are followed, the amount of vulnerabilities will naturally fewer and, when they do occur, much less likely to have downstream effects, while being more easily maintained.
Rust as an amazing system-level language. It is a C-level language. Other languages based on Rust are coming down the line at some point. NodeJS linked-libraries are being written in Rust as well as Web Asslembly. Web Assembly is a compile target of Rust for web applications.
Rust has a TON to offer the software community.
immutable variables in rust only guarantee compile-time immutability. They can be modified if the program is hacked. On linux you need to mmap a memory region and use mprotect to prevent the data from being modified at runtime.
hey mr. Sr Software Engineer, could you explain how local variables in a function which are on the stack are immutable at the binary level?
@@apestogetherstrong341 I get what you meant but that *can* actually happen in both Rust, C, and other languages. It's called "const promotion". Basically, when the compiler recognizes that it's safe to perform the calculation at compile time and store the result in the compiled binary as an optimization even though you didn't use explicitly use `const`.
That said, Rust *does* help to give the compiler backend more freedom to do stuff like that by making stronger promises about how things will behave. (And, as such, it'd also be more amenable than C or C++ to automatic insertion of calls like mprotect.)
@@ssokolow well, const promotion can't happen with something like "let x = arg_1 + 2", in that case it's just incrementing the stack pointer and moving to it. But yeah, i get what you meant too
@@notuxnobux If you change a value of immutable variable via hacks or something on runtime you will probably introduce a UB in the program.
exa is available in the official Arch repos, not just the AUR.
You can just use cargo, installing it is realy easy, like easyer than npm in my opinion.
@@Muttisuri Of course you can, I just thought I'd mention it was in the official Arch repositories because DT said it was in the AUR.
@@Muttisuri yes you can use cargo but tbh using the package manager is better because updating the packages would be much easier as you dont have to keep doing cargo install --force every time theres a new update for exa
@@Muttisuri Why not just use an AUR helper like Paru?
@@raphtlw
I'm not 100% sure but doesn't cargo update the package if it finds a more recent version?
Excellent list. One more: delta -- a viewer for git and diff output - 🦀⚙️ - it is fantastic. Thanks for doing the video!
I struggle to keep up with all the new CLI tools in the ecosystem... so it's great to just watch a roundup video like this one. Thanks and looking forward to more roundups!
The best thing about ripgrep is, that it is insanely fast! Very useful for searching a string in a file recursively.
Getting started on Rust:
Step 1: Gather some resources with your rock
Ily
Aye, I never made it far with my rock. Were good days playing it.
Vscode already uses rg for its workspace search feature IIRC. It's simply too much faster than grep to ignore
Dude, I absolutely love your channel. I've been an emacs user for seven years and switched to doom about a year ago before finding your channel. I always learn something useful from your channel and this vid is no exception.
Go and Rust are popular modern systems programming languages for a reason. Built in build systems, package management, and testing suites lead to building robust fast reliable software very quickly. Just look at how fast the Pop!Os team can pump out really good systems level software with some of the best runtime safety in the game. Go routines provide a revolutionary way to implement concurrency. So many benefits behind these languages. They also lack all the "history" and backwards compatibility bloat issues that languages like C++ have. Referring to these languages as "memes" merely shows a drastic misunderstanding of what they accomplish.
Go is not for systems programming.
DT: "I am not a programmer."
Also DT: *starts programming in Haskell*
All I am waiting for now is a window manager written in Rust. Thats all we are missing
There is LeftWM
Even Microsoft is starting to rewrite Windows in Rust.
Meme?
@@rahilarious doubt it
Word?
They aren't trying to rewrite windows but they are experimenting,how well Rust could fit into their ecosystem. medium.com/the-innovation/how-microsoft-is-adopting-rust-e0f8816566ba
they started rewriting a couple of years ago. Now they are developing an open source clone for them to use as well. Search for project Verona.
You’d probably like the bat-extras repo. turns tools like ripgrep and man into batgrep and batman. so nice. also works well with diff-so-fancy.
Great video also with great comments by viewers. I've installed all of these on Raspberry Pi's and m1 Mac.
Good video, always enjoy the CLI stuff. Better to me than distro hopping videos.
He's DISTROtube
@@elinoamrichter162 Yeah I know, just stating my opinion.
@Grisosthone No, I have many, you're right, I cannot have ONE !!!
@@jessegodsey Keep talking like that and you're gonna get yourself cancelled
@@kieranwoodward575 Lol, o.k.
Tokei actually also recognizes embeded languages. So if you have javascript in your html it shows that as separate.
that's so cool 🤯
> I don't see why anyone wouldn't just replace `cat`
Because it works just fine, and you really shouldn't be using it for reading files at the terminal (use `less`).
Rust's advantage over C is its memory safety. `cat` is already memory safe. Thus as a user, there is no advantage to me switching.
I really hate when command line tools have no man page.
Ripgrep has one. You just have to use rg instead of ripgrep
@@Ricojo777 I was talking in general actually, this video just reminded me. But thanks for letting me know! :D
I always thought man pages could be a whole lot better. include the top 10 useage examples for one idea
@@randaldavis8976 It depends on the man page. For example, Linux programmer's manual have some nice usage examples.
Anyway, I think you might make use of `tldr` command
@@randaldavis8976 pipe it through bat. It improves it :). Then in fish, make the bat an abbr for man, and there you go, it will always do this for you no extra typing
I have been running bottom as a rust replacement for htop and it looks really nice with a lot of good info.
DT showing rust programs in a terminal made in rust.
Alacrity is written in rust if remember well
In a rusty computer, and that'd be perfectly rusted.
A year and a half has passed since this vid posted.Amazing stuff going on in Rust.Pkg's,like alacritty DT did showed us what cpu accelleration accomplishes.Rust doesn't do null reference (Tony Hoare conjured that up in 1965.Stated in public forum 2009 that null reference was $billion mistake.)Valid Rust doesn't,anyways but one can try unsafe Rust to get through compilation.Hazard pointers need to be dealt with correctly,though,or panic/crash at run time.Rust doesn't do garbage collection. 100% thread safety.Suscinct error handling.Zero cost abstractions.Rust compiler expects all but absolute perfection or no compilation.Even details minor 'errors' at run time,if any. ie #[error(unused-variable)] concider using '_' .The detail in Rust compiler info is something else.
Even most experienced computer science phd's get stumped here and there in Rust.This language is a whole new ball game even though it's C++11 and C++20 at core.
Alien/Greek to those familiar with earlier computer languages.Cat's out of the bag now and those who bawked before now realize they better get on board or get left behind.Rust stuff coming faster than tutorial vid producers can deep dive into it. async/await concurrency is revolutionary.It looks like Rust is going to blow the lid off everything ever written code before.
Ignoring the discussion c/c++ vs rust, the problem I have with these rewrites is that they often change the default behavior and interface. There most probably is a reason why tools behave the way they do, even if you as a user don't understand or know it. cat, ls, find, ... are all POSIX standard utilities the system and a lot of software relies on that you simply cannot mess with. You want to reimplement gnu or standard utils? Fine, but retain default behavior and the interface. Otherwise, do not advertise them as replacements, bc they are not. They are alternatives, but not replacements.
@@bigpod replacements have exactly the same behavior and are completely interchangeable. Not the case with most of these rewrites. It's like changing APIs or interfaces. If they do not behave exactly the same, they are not interchangeable and thus not replacements. Also you should care about standards like POSIX because they guarantee interoperability and portability. But then again, if people do not understand the crucial importance of stable APIs and interfaces, and why there have to be reliant contracts for IPC, then they shouldn't program essential tools or services in the first place. Changing well-known, reliant and expected behavior, just for the sake of being different and promoting one self's ego (I know better, I do it my way), will break systems and make maintaining interoperability between processes a nightmare.
@@bigpod try the following then:
$ sudo cp -f ~/.cargo/bin/bat $(command -v cat)
$ sudo mkinitcpio # on arch, or update-initramfs on debian, check your distro
$ sudo reboot
With my understanding of replacement, this should work flawlessly, but then again, my understanding could quite possibly be flawed. Chances are, your system won't even boot anymore, because 'cat' is an essential binary used in the initial ramdisk to boot practically all unixoid OSes, which is possible thanks to standardization like POSIX. But since you do not care about standards, interoperability and portability, having to repair constantly breaking and non-functioning systems is probably not a problem for you anyways.
@@onehaxxor8574 bat works exactly like cat when not in interactive terminal output, check before talking ?
the difference is that
C is a programming language with
the most basic features from the 1960s
these features allow you describe low level stuff
C is basically a template language for good programming patterns in ASM
but this comes without safety and is prone to produce all sorts of damage like segfaults
Rust is a programming language with
sophisticated features from different languages
including Programming Language Theory (research)
including the experience of the last 30 years in the industry and lessons learned in C++
also allows you to describe low level stuff
its memory model protects you from segfaults without producing any runtime dependency (due to that ivory tower research that hackers tend to despise)
basically C is garage amateur carpentry while Rust is space tech engineering.
No doubt. I've been using exa and starship for a few months now. And now om deffinitly going to use the rest
my man stole luke's beard
You should check out nushell. It's a shell written in Rust. It's now at minimum viable product status.
I doubt you'll use it as your main shell any time soon, but you may find the general concept to be interesting. Like fish it isn't aiming to be POSIX compliant, but is instead trying to evolve the shell as we know it.
He did
@@JosueRodriguez08 It's been a year since then. Probably worth another look.
@@IcarianHeights Right now? Probably. Long term, who knows. That said, nushell isn't trying to be a PS clone, it's just borrowing some of PS's concepts along with others (such as the functional programming paradigm).
it's not just a "less"-feel for e. g. bat command (and I would assume probably the process listing one, too), it literally just pipes into "less".
AFAIR, the choice of pager is also configurable; might have some kind of environment variable.
The only true con of Rust is that Gentoo user will wait more for their software to compile. Rust has a lot of pros (security, speed, compiler errors, memory management, ...) even though purists will always prefer C and Go may be seen as simpler.
Nobody who really prefers C should be called a purist. It's about the most impure language one could create. (Spoken as someone who's been programming C since the 80s....)
@@peter9477 What do you mean by "impure"?
@@charlubermensch2395 You used the term "purists". In that context, I used impure to mean "the type of language a purist would not like".
rust-bin.
Hey DT. You do know that Rust comes from Mozilla Research. I repeat: Mozilla ;-)
Assuming you aren't trolling here there's a clear difference between Rust, a programming language and Firefox, Thunderbird, etc which are internet programs.
Rust is a programming language, it is harder to censor and almost conpletely pointless to do so anyways because of the abundance of other programming languages which aren't censored.
Mozilla's other software like their browser and their email client are much easier to censor and there is a motivation to do so.
@@hostgrady It's called a joke ;-)
@@gotchaxp so you were trolling? Ok well thats good
Rust isn't part of Mozzila anymore. They are their own faundation now.
Congrats for these Rust pearls. Now...waiting for the part II of these Rust pearls...or the review of Redox, the OS written in Rust.
Hey DT, I would like to see a REDUX OS review of Yours about that linux distro since we are watching RUST things now, would be very interesting.
The reason your .bashrc didn't show up in fd is because fd ignores hidden files by default.
Also fun fact - bat uses less under the hood (and i'll guess that procs does as well)
extra fun fact: you can add the -u flag up to three times to make fd ignore less and less files. if I *really* wanna make sure, I run fd -uuu
Sorry, but judging by the output of bat, it's not a replacement of cat, but for something like less or more.
Because when using cat, you only expect the file content to show up on stdout. That's necessary for piping as well.
This is my thought as well. Bat is nice but not a replacement for sure.
@@koderkev42 bat checks for the output method first, that formatting only happens in terminal, not piping; read the man.
Can I ask why you have the super hardcore mixer / sound setup in the background? - you could master Bon Jovi with all that - its not podcast / youtube stuff :)
You know there is even an os written in rust called "redox".
I have all of them installed! And use it often!
Very cool! Thank you. If you find more please do another video.
Bat just looks like nvim -R or Vim but with less functionality. Which you could easily alias to "nvR", "nvr", "vir" or "viR" inside your bashrc file.
How do you get those awesome "images" when you start up your terminal?
As a Rust lover and enthusiast, I'm very pleased to see this video on your channel)
I haven't programmed anything serious on Rust, but as far as I have seen about the language, it seems to be a modern and better version of C++, I have programmed on C++ since before C++11 was a thing and by today's standard C++ has became a very bizarre language.
For example on C++ is a best practice to mark every variable as «const» or «constexpr» unless you need it to change while on Rust variables are «const» by default and you only need to mark them as «mut» when you need it.
Some people have said that “Rust is not as efficient as C++” by comparing the ASM output of same codes, but that is not true, the compiler might not be as efficient, but IMHO the language is as efficient as C++.
For which code Rust outputs worse ASM then C++?
@@ekremdincel1505 Sorry I can't find the video where I found the original source, but I remember the video comparing the output of the same program using godbolt.org/
Let the tools written in C rust in peace ;- ) Jokes aside, it is an interesting and inspiring video.
the standard find command also has an --exec to run additional commands with the find results.
If someone ever rewrites emacs in rust, hopefully they will take the best parts of emacs & the best parts of vim and combine them.
Even Pop!_OS is making their own DE in Rust!
alias bat="cat" is bad advice, since you couldn't pipe the contents of a file in an interactive shell using cat anymore. Better use alias cat="bat -Pp" instead.
Hi mate. time stampts might be useful in this video :)
i want to create my own distro, create my own command, my own planet, my own universe, my own species and my own dna
Rewrite GCC in Rust.
...
not a bad idea to write newer compilers in rust if the rustc wasn't depending on llvm
@@basedfacistman The whole point of having a compiler with same programming language will then be ignored. There is no point of rewriting something to reproduce same output (grown compilers such as gcc will take years to fully replicate in other language if not giving up before).
It's like you are telling someone to rewrite something just because rust is superior, in the end will it be worth it?
@Nate Higgers That's one thing I hate about rust binaries. I remember one day when I used a musl static compilation to get a >60 mb executable for an ftp client, where In c++ I managed to get 4-5 mb
There is GCC frontend for Rust,you could have a look on it.
Rust is basically C++ with an extremely strict compiler with far improved error messaging for developers. Rust is focused on avoiding bad security practices. You cannot compile code that has glaring security problems. It will stop and force you to fix your code and it Is pretty good about giving you a meaningful error message for the compile failure. Rust is far more opinionated and security focused than C++ which allows a developer to do whatever they want without much complaint, providing it compiles. Rust will stop someone from compiling bad code. Rust won't remove all security issues but it covers the big ones that are most common among most security exploits. This is why there is so much talk about using Rust for systems programming such as an OS kernel. Linux is looking to allow device drivers to be written in Rust. But that isn't the only reason to choose Rust for any development project. It's a very nice language and that compiler still gives you much better feedback when a compile fails. Lots of people have been dipping their toes into Rust and that is why there are so many nifty Rust programs. Rust programs can be highly performant.
bat seems like more of a less replacement than a cat replacement, unless it behaves differently in scripting contexts. The thing I want out of any cat program is 1) it outputs all the characters from a file in order, and 2) it concatenates the things I give it. The formatting makes it kinda useless as a cat replacement.
It behaves differently in scripting/piping. you should check it's docs, they have some nice options.
Cat is one of the few things in GNU Coreutils that doesn’t have any colorization in its output. Even ls is starting to use colorization by default in most cases. Disabling the colorization is pretty easy. There are a few fairly standard ways of testing if a file descriptor is connected to a terminal.
I believe ripgrep already covers most of the use cases of fd with "rg --files".. I often pipe that to "rg [string]" to find files
Can you do a video on wtftw, a wm written in rust.
I ve got an off topic question, as you are using the ergodox. There is something like the zsa moonlander have you ever heard of it if yes is it likely that you would give it a try if the one you currently got for example broke? Unfortunately there aren't many user videos and like reviews so that there would be more than just first impressions...
There are quite a decent number of reviews now. One guy even specializes in it. Just search for ergodox vs moonlander. A british guy did a fantastic review of both. There are some major differences, and I mean really significant to consider. I would tend to say moonlander si better, but ergodox also has ome points going for it. It depends what you want. I ordered my moonlander a week ago. Still 1 month to go till I receive it.
Major differences I found: moonlander is more compact; better for travel. The thumb area swivels, this is more ergonomic and also allows for adjustment for smaller/bigger hands. Thumb area has better key redesign. Moonlander has RGB on every single key; not so on ergodox. Lot of keys do not have RGB. RGB is thicker, more robust and also since thumb area does not pivot, it has 1 less point of breakage in the hinges. In fact the reviewer in the youtube video I mentioned - his hinge on the thumb pad broke. Could have been a defect though. Moonlander uses type c cable (not that big deal though). Exterior row on each side has keys that are less wide on the moonlander, bringing the center point where you press closer to your finger, which could be important. These are some major highlights. Cost is the same. It was here, on DT video I learned of the ergodox and subsequently bought the moonlander! Super excited.
You cannot replace cat with bat. Cat is useful because you can pipe from it, piping from bat is like trying to pipe from less.
You are mistaken, check their docs
Think it's the fact that it has manual memory management and it's not very verbose. People love it and it's pretty swift.
Great stuff. I always seem to get something good from every video. I don't have a linux machine right now, but I have been putting all of this knowledge to use in my WSL/openSUSE setup. Granted, not everything wants to run on Wayland, but most things do it just fine.
A quick edit of my alias list and I can now see folders and files by color and sorted. Before, I couldn't tell a folder from a file. Awesome.
For FD, I set an alias for "find" to search where I am and I set "search" to search from the / directory. Sweet.
Hey dt! Could you take a look at the ion shell?
Pretty sure people are switching to rust because it removes the performance issues of C++. As well, its syntax forces you to write clean code. Don't know the C family myself, but would definitely choose rust to learn if I were to pick it up.
Not really. The performance of C++ is not an issue. C++ is very performant.
It's really just the modern syntax and concepts that lets you write safer code with not that much effort, without sacrificing performance.
In my experience Rust and C++ perform about the same (very close to C). I find Rust far more pleasant to work in though. I tend to write code faster in Rust, in part because it doesn't need as much boilerplate as C++. I spend less time debugging Rust code too.
And unlike in C and C++ getting 3rd party dependencies is not a realm of incomprehensible suffering. You just declare what version of the package you want to use and it works.
@@whenimnotaround If that is the case, why are still a lot of video games written in C, precisely for the reasons because it gives them more performance?
The linux kernel and most of the linux programs used to be written in C which is a very old language and even for those with experience it can be hard to write code in C, rust is a new programming language which can replace C because it's also low level, so it's very fast (not faster than C but close) and it has some features that make it easier to code in.
Recent benchmarks have shown that Rust can be faster than C. However, I don't think of Rust as a C replacement but an addition to systems programming. There will always be scenarios where it'll be preferable to use C/C++ in systems programming. Rust allows you to write low level code in a precise, short and abstract way - that is brilliant. But it also has very strict rules and sometimes doesn't let you do "your way of programming". Nevertheless, I do most of my programming in Rust. I just don't think of it as a replacement
@@lieywe3438 How can it be faster than C? Is it a compiler issue (poor optimisations by C compilers), or is it the langage itself? It seems to me that C is closer to machine code than Rust. So I don't get how Rust could be faster.
@@brinckau Rust, as a abstract language, has more optimization opportunities than C, the abstract language. It is about language semantics.
And C is not more close to the hardware than Rust, they are same.
@@ekremdincel1505 Assembly is not an abstract language, is converted to machine code without any optimization, and yet cannot be beaten in terms of speed (because in the end, everything is machine code, so writing machine code directly, or assembly code, makes it possible to do exactly the same as a C or Rust program would do). Provided you're good enough to write excellent code, of course.
So I'm not convinced by your argument about optimization opportunities.
I also believe that C is closer to machine code than Rust, because Rust has more abstractions than C. Otherwise, Rust would not have more optimization opportunities than C.
@@brinckau Every language is abstract. I mean the formal definition of the language regardless of current implementations.
I didn't even say anything about assembly in my previous post.
You can write inline assembly in Rust.
Rust's abstractions are zero cost. And having useful abstractions not necessarily prevents you from having tools for writing low level code in your language. Rust have both safe references and unsafe raw pointers, for example.
"So I'm not convinced by your argument about optimization opportunities."
An example about language semantics:
Rust inserts C's equivalent of "restrict" keyword everywhere, thanks to it's borrow checker, and this gives the more optimization opportunities. People use the "restrict" keyword in C so rarely. Not everything is theoretical.
People love rust because it can be written at a pretty high level but without the disadvantages of other similar languages like go because it's not a garbage-collected making it wicked fast.
Awesome tools! Thanks for sharing
there is *git-delta* which is a better diff, you can configure it with git and then see the diff in color, custom color schemes, and even side by side diff, with numbered lines on each side. It goes great with *bat*.
Not a programmer by trade, but until now, I come to love every Rust program I ever used. Fast, efficient, easy to use. _fd_ is such a breeze compared to the standard _find_ command. _exa_ has won my _ls_ alias.
I'm still looking for a window manager written in Rust. Will you dive into that, DT?
look into Windows 10, my guy
@@itsamcb Not really. Windows 10 was one of the most important reasons for me to switch to Linux. 😂 Seriously, is anything about Windows actually written in Rust? I thought it was all C++?
@@marioschroers7318 what he is trying to say is that if you love bloated stuff over very efficient and already working standar tools the you should as well go ahead and get windows
@@JosueRodriguez08 The things is that, for instance, ripgrep and fd are much more efficient than their standard counterparts (see their benchmarks on their github pages). All of that with better memory guarantees. Go ahead and go use "more" instead of "less", why not.
@@JosueRodriguez08 Ah, the bloat meme. Didn't catch it this time. Gracias por explicar!
Also check out bottom: a bashtop like replacement for top.
bat vs cat - is If "bat file | grep 22" will get lines with 22 or line 22 too? How much slower is it?
same question with all of them - old gnu utils can be chained - can these? Will they break old scripts?
bat is designed to turn off all its fancy features and behave just like cat if you feed it into a shell pipeline.
Hey DT, what's the best AUR helper?? Is it yay, because it's 3 letters?? Or is there more to it??
For Arch based, I much prefer Paru to Pacman.
Rust language would be my top choice for a programming language to be stranded on a desert island with a laptop and solar powered battery recharger - if could have only one language choice. It's intrinsically versatile enough to be applied to about any programming domain - with Web Assembly support, could even be used to write programs that run in the browser. And presumably being stranded on said island, would have plenty of time to master its borrow checker and annotations - and the cool kids stuff like pattern matching and other functional programming features. And finally get around to learning how to write macros in its powerful macro sub-language.
haha it's COVID time, we're all stuck on an island...your wish came true...get cracking....as for me, I live offgrid in the mountains in Canada, so, pretty much the scenario you already describe....
You'd have plenty of time to program, on this desert island, for about a week, until you became so weak from lack of food that you couldn't type any more. :-(
@@peter9477 Well, everyone in the West will be looking at that scenario by around late summer
I liked most of this programs but I'm not switching to most of them because if you run for example cat the file stays in the terminal but with bat when I quit it isn't above(it don't stay in terminal) same with Procs
bat uses your $PAGER (less by default) to display its contents when in an interactive shell. This can be bypassed with the -P option, or configured to use a different one, or none.
@@davidh.4944 Thanks! Now I can switch to it.
Nothing better than C. By the way replacing common aliases won't facilitate bash scripting portability.
Have you tried Rust?
C and Rust > everything else 😎
@@bigpod I am not worried about DT and I appreciate its content even though I can have differing opinions. His audience should be aware that exa is not the same software as ls; both programs perform differently and both programs take different arguments. I don't think it's a good practice to let pretend that an application is what it isn't. That being said someone can still bypass aliases using quotes or backslash. Knowing this, people are free to do as they wish.
the real question is when rust will be rewritten in emacs lisp
Soon
colorls is a ruby port of ls. I think colorls is better then exa because it has all of exa color stuff but it has file icons and has the date of the file that changes in tint based off date
Maybe lsd? (lib.rs/crates/lsd) I wouldn't want to have to wait for an ls replacement to wait for Ruby or Python or whatever else to seek around, gathering its files, if I'm still on an SSD-less machine and they're not already in the disk cache.
Cool. But are these more efficient in relation to the added features or just more colorful?
I can't say about all of them, but ripgrep is specifically designed to be faster than all competitors (there's a whole blog post linked from the README going into great detail on it) and, while piping things through pygmentize is known to be a bit sluggish, bat uses a syntax highlighting library named syntect that's specifically designed to be lightning fast.
A big part of it is that they want to write Rust code but they don't have any original ideas so they pick an existing tool that they think they might be able to enhance.
Thank you so much. It is really so handy programs.
I would probably start using these all right away, but much of the work I do is on company servers into which I cannot install what ever I fancy :/
So I think that except for Alacritty and Fish shell, I have to stick with the old ones for now so I don't remember which commands are available on which computers...
Thanks for the list though, it is nice to see that more and more Rust programs like `bottom` to replace `htop` are coming!
Often, it's preferable to stick with commands that are standard/default to most machines. Getting efficient/proficient with those "standard" commands offers much higher "return on investment" because that skill is more "portable". So while all these tools are cool, it's not cool enough for me to invest on them and abandon the more widely available standard commands.
I tend to agree with sticking with the POSIX standard tools but would point out that these rust tools are statically compiled binaries that you can copy around via scp/ssh and run them arbitrarily without even needing to install them into a standard $PATH.
Cant imagine doing this for a prog written in python or node/typescript however.
The package name for fd is fd-find!
DT you amaze me..... you are very good at this.... I am learning at such a high pace because of this...... if you enjoy doing this channel please keep going😎
Why does it matter what language a tool is written in? And while we are at it: Why Rust > Go?
One reason mat be that Go is a garbage collected language. Though i’m not sure about its performance so what I’m saying may not matter
You have to feed the cults! You can have a bad design written in the fastest language and it could still run slower than a good design written in python
Rust > Go if you don't consider the developer's time.
whatever may be rust is just rust it cannot replace c programming c programming is giving more developers more power and control
Fractal is a GTK Matrix client written in rust
Most importantly, Rust is secure. Something like the recent sudo bug is almost impossible
hahhahahahahaha good one
@noname Whats so funny?
@@LabiaLicker There are a lot of reasons that statement is an oversimplification, but an /etc/sudoers parsing bug isn't one of them. Parsers are the first Firefox components Mozilla started rewriting in Rust because it's so well-suited to writing memory-safe parsers.
Sure, anyone can abuse `unsafe` and be an idiot, but writing a parser typically isn't the place where people think it's necessary and a good idea.
Let it mature first and we'll see. It's pretty obvious to everyone who is not part of the rust cult so far that there will be many issues. No one is arguing the language is good. The language also has a lot of future. It's just at this moment it's far from being the thing people claim it is and it is about to be.
The presets are nice but the power of GNU tools is not their single unit efficiency but their composability. it's much hard to compose things that have tons of post-processed output because the post-processing adds things that aren't usually there Arguable most people don't use GNU tools like that or know GNU find can exec on a file. Granted all of this rust application absolutely do that its just it is less intentional here and they are not doing them now
Thank you for bat
GNU/Linux is slowly becoming SomeCoreUtils/Linux :D
GNU/Linux is slowly degenerating to Windows on steroids
There always have been alternatives to GNU utils. And that's for the better, GNU utils are often bloated… which isn't quite improved with these Rust alternatives.
4:36
rickroll alias?
XD
thank's this was very good
what distro is he using? looks pretty slick
2:08 Why do youtubers use “clear”? Is there a benefit to it instead of using Ctrl+l? I’m genuinely curious. ‘Cause I’m so confused that you use a window tiling manager to be “productive”, saving every keystrokes as possible, not using a mouse, but still types “clear” in the terminal, which I think is commonly used. I’m not being rude really. I’m noob in Linux so I most probably am missing something.
He uses vi key binding in the shell, Ctrl-L does nothing there.
In zsh with vi mode ctrl-L works
I didn't know that Ctrl-L is not default for all terminals/shell. Good to know. 'Cause every distro and/or DE I tried with the built-in terminal, it just works. I'm also using vim keybinding in the shell (zsh) and Ctrl-L still works. I didn't rebind it or anything. Also, I understand if it's really for the youtube video showing what he's doing for the viewers. If that's the case, then that's totally a valid reason.
Huh, I’ve thought you were a programmer since I started watching the channel. Do you do youtube full time? Or do you have a day job?
Dt used to do retail full time and youtube as a hobby but now he does exclusively youtube. He has also never been a programmer by trade he's said it a lot.