@vbabka I immediately got a “Stack overflow” and the println! only went 3 deep. Maybe it was smarter to know it would go further?

@acmel Rust is very much becoming dominate (especially by my employer). I like the guarantees that Rust brings, so I’m working on learning it. I bought a book on Rust, which really gets into the details of the language, but honestly, isn’t a good way to learn the language. I found that learning by example is a much better approach.

I have a non trivial program I’m writing (it was one of the programs I had to write for my interview), and I’m hitting all the fun corner cases with it. I’m trying hard to keep an open mind, but for someone that’s been programming C for over 3 decades, it’s really hard to do so. ;-)

@ljs @acmel I thought that cover said SYSTEM ADMIN

And today I learn that Rust does not like recursive functions :-(

(In user space, I’m recursive function happy!)

@acmel @ljs I was thinking of shimmy()

Continuing my Rust Rants :-)

It’s unfortunate that move is a keyword. As I write my little programs, I found that that’s a common function name I use. Now I need to come up with something else. adjust ?

@mripard also, this is really the exception and not the norm. I find saving these programs in subversion (svn) is more convenient than git. It's best with a central repository than trying to keep several machines in sync.

@mripard I totally agree, and why I've been an advocate. But I like to write these small programs, sometimes to just learn and sometimes to do a small job. All these are mostly throwaway code (but I keep for reference). In this case C/make is so much more convenient than Rust/cargo.

There’s gotta be a better way…

use std::env;
use std::path::Path;

fn usage(arg: &String) {
    let path = Path::new(arg);

    println!("usage: {} a b", path.file_name().unwrap().to_str().unwrap());
}

fn main() {
    let args = env::args();

    if args.len() < 3 {
        usage(&args.collect::<Vec<String>>()[0]);
    }
}

@mripard Yes, I found that. But you still have the extra step of creating the directory structure. It’s possible, but still annoying and not as trivial as C. But I guess that should be the tagline for Rust. Not as trivial as C

@mripard Yeah, I found that. Still not as easy as just creating a bunch of C files, and typing make foo and if will compile foo.c

Using the holiday break to learn Rust, I'm getting frustrated with Cargo. I mean, with C, I have a bunch of small programs that I use. But it seems that with Rust, to do the same, I have to make each one into a separate project, which I find overkill. Is there a easy way to make 100 little programs without making a 100 little projects???

@monsieuricon Will it affect what apps to use it with?

@monsieuricon Honestly, I have no idea what the difference would be.

@wagi Because only the Linux kernel seems to care about not breaking user space.

@ljs ktest's make_min_config
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/testing/ktest/sample.conf#n1286

@monsieuricon @mattblaze there's been several times I found news about things I was unaware of from social media, as my news feeds always try to predict what I'm interested in (forcing me into a bubble as it's based on what I click on). I enjoy seeing articles posted by others as they are not usually within my normal interests.

That was fun. Added two more HDs to my workstation, but accidentally unplugged the power of one of the existing HDs. Thought the new HDs caused my existing md-raid1 to get screwy, and I had to re-add to the existing array as it was down a drive. I accidentally picked my external backup drive (blowing away all my backups). When I finally noticed, I shutdown the machine, plugging in the HD and on booting up, it picked the HD that was powered off as the main drive for the raid1! I spent a good half hour fixing all this. 😛

@joe-lawrence Emacs is more than an operating system. It’s an orchestra.

And the say emacs is crazy.
https://hackaday.com/2022/12/16/foot-pedal-ups-vim-productivity-brings-ergonomic-benefits/