this post was submitted on 18 Dec 2024
836 points (97.8% liked)

linuxmemes

21601 readers
670 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    836
    Linux and Chill (lemmy.world)
    submitted 4 days ago by Clbull@lemmy.world to c/linuxmemes@lemmy.world
    93 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] 01189998819991197253@infosec.pub 48 points 4 days ago (2 children)

    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.

    [–] Pickle_Jr@lemmy.dbzer0.com 7 points 4 days ago (1 children)

    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?

    [–] SlopppyEngineer@lemmy.world 8 points 4 days ago (1 children)

    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.

    [–] syklemil@discuss.tchncs.de 3 points 3 days ago

    Socks were invented to be used in sandals, it's the one true way!

    (Typed wearing big woolen socks in birkenstocks)

    [–] mycall@lemmy.world 4 points 4 days ago (1 children)

    Bonus points for some Rust device drivers.

    [–] 01189998819991197253@infosec.pub 1 points 4 days ago (1 children)

    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.

    [–] snekmuffin@lemmy.dbzer0.com 2 points 4 days ago (1 children)

    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

    [–] 01189998819991197253@infosec.pub 1 points 3 days ago (1 children)

    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?

    [–] syklemil@discuss.tchncs.de 5 points 3 days ago (2 children)

    The serious answer here likely has several components:

    1. 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.
    2. 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.
    [–] 01189998819991197253@infosec.pub 2 points 3 days ago

    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!

    [–] Croquette@sh.itjust.works 1 points 3 days ago (1 children)

    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.

    [–] syklemil@discuss.tchncs.de 2 points 3 days ago

    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.