Put the gun away and throw that cpp book in the bin, fool. I brought The Linux Kernel Programming Guide, which is in C, and my own socks, which are wool. Now let’s gets crackin.
I already use linux. My feet have been getting cold lately. it never occurred to me to get wool socks. Is this how it starts? Are skirts next?
Unless you use goat wool socks. Then you can go for a old school hippie build. Sandals, long hair, tie dye shirt and go from there.
Socks were invented to be used in sandals, it’s the one true way!
(Typed wearing big woolen socks in birkenstocks)
Bonus points for some Rust device drivers.
Never touched rust, so I don’t understand the hype. I’m not arguing against it, mind you, but I’m gathering, more and more, that it’s worth a look. Maybe I’ll look into it after work.
even all of that hype about memory safety and borrow checker you keep hearing aside, the actual coolest thing about Rust is how it does Traits instead of classes and that you can bind arbitrary data to enums
Really? That’s really cool. So, what’s all the hate? Is there any actual merit to it, or is it just an “I’m better than you because I just am” mindset?
The serious answer here likely has several components:
- Some people and businesses have invested a lot in languages that governments are now trying to deprecate. When someone is told that their assets may be stranding, and please move on to
$NEWTHING, they’re likely to get … grumpy. Both they and the government may be correct here, even if they’re at odds—they have different scopes and concerns. - Differing values. See e.g. Cantrill’s “Platform as a reflection of values”.
- Rust highly values correctness, which will feel like a straitjacket to a lot of people.
- It also moves as much error detection as it can to the compilation stage, which won’t sit well with people who want to get something out the door ASAP and then find the bugs as they happen.
- So it also encourages tackling complexity early rather than kicking the can down the road, which again isn’t to everyone’s preference.
This is a very detailed answer, and I greatly appreciate it. So, the subpoints on point 2 are benefits in my eyes. Just another reason to delve deeper into this language. Thanks!
More than half the points are just good engineering practice directly embedded in the language.
It tells a lot about the state of programming in general with the pushback we see with memory safe languages.
I’m down with Rust and I can’t wait for official support for embedded Rust in chip manufacturers, because until then, very few clients will be okay with using unofficial Rust cargos for their products.
Yeah, that’s the correctness focus. Some people dislike it as a straitjacket, some even take it as a personal insult because they see it as a skill issue. They, the good devs, shouldn’t be held back like that (spoiler: they aren’t as good as they think they are).
Personally I like that aspect of Rust, but I also write Python with a typechecker and a loong list of enabled lints in
ruff. I can get the happy path done without it, but having just the happy path often isn’t good enough.Enforced correctness helps a lot with confidence for those of us who know we sometimes make bad assumptions or forget some nuance or detail. But it will be absolutely infuriating for people who can’t stand being told they made an error, even one of omission.
- Some people and businesses have invested a lot in languages that governments are now trying to deprecate. When someone is told that their assets may be stranding, and please move on to
Girl, I will wear whatever socks you want, but… pulls out my own gun. We’re reading this damn book instead.
Why no K&R?
/s
Lol. I prefer the New Testament.
Don’t kink shame her
how does it compare to k&r (2nd ed.)?
Honestly, I prefer King’s book to any other for intro to C programming. K&R is a classic, and is really quite good for diving into some cool tricks (i.e. postfix operation wizardry).
But as a beginner, I can just say that King’s book is much more digestible. The author holds your hand a lot more and assumes you only have a basic knowledge of programming and the UNIX command line.
That said, the exercises and simple projects do push you to demonstrate what you learned in each chapter as well as enforcing other Computer Science fundamentals like basic data structures (stacks, queues, linked lists) through demonstrations in the C language.
My plan is to revisit K&R after a few other books in C like Advanced Programming In The Unix Environment, Unix Network Programming, and The Linux Programming Interface. All while referencing Beej’s Resources.
I feel like by then I’ll hopefully have a more solid grasp on C and can then more aptly appreciate The K&R Book.
I better be getting pegged at the end of the night if she makes me suffer by writing C++.
In C++? I’d rather be shot, thanks :P
All Linux enthusiasts are attractive women.
Even if they are men?
Especially if they are men
I’ll settle for girlish and overknees
I appreciate the usage of the pi 1 and not one of the newer versions.
Maybe I’m just old but old pi was special
Pi 1 was an amazing idea, I ordered one as a sonon as they were available and then never used it for anything. I’ve bought way to many pis since then.
It was! I still have mine somewhere in the house. It was my kodi media player for a long time.
Seriously though, anyone knows the source of the pic? I’ve been wondering for a while.
Nothing says “I love you” quite like a surprise LFS install.
When you find out your partner is into BDSM…
Bad trigger discipline
Here’s what we’re gonna do. We’re going to do the equivalent of x11 application network transparency but with wayland.
Kind of like streaming a desktop with sunshine, but on an app by app basis.
Also we’re gonna make a client that work for it on android, windows and in a browser.
Then I’m going to fuck you in the ass
its more intimidating
My type of stay-at-home wife works on OSS projects all day
Could’ve got me there quicker by telling me the truth
w o u l d
Absolutely. Put the gun away. You got me at nerdy.
she had me at “socks”
please don’t make me read another bjarne book. the last time i read one it made me want to stop programming
Am I going too hard by making shortcuts to start and stop SSH on my steamdeck desktop for easier file transfer? Feels like a basic security step when connecting to other networks, while not wanting to remember the commands to enable, also wanting to avoid keeping the perms permanently open for the sake of unknown backdoors. Even added windows stating if it was started or stopped in the case of extra sauce or herb.
Ayy girl, we’re going over and beyond with your network security, because we all do a fucky wucky from time to time.
