• 𝕸𝖔𝖘𝖘
    link
    fedilink
    English
    233 hours ago

    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.

    • @[email protected]
      link
      fedilink
      12 hours ago

      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
        link
        22 hours ago

        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.

    • @mycall
      link
      143 minutes ago

      Bonus points for some Rust device drivers.

  • jawa21
    link
    fedilink
    82 hours ago

    Nothing says “I love you” quite like a surprise LFS install.

  • z3rOR0ne
    link
    fedilink
    25
    edit-2
    4 hours ago

    Girl, I will wear whatever socks you want, but… pulls out my own gun. We’re reading this damn book instead.

      • z3rOR0ne
        link
        fedilink
        4
        edit-2
        1 hour ago

        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 wizardy).

        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.

    • @foofiepie
      link
      13 hours ago

      Absolutely. Put the gun away. You got me at nerdy.

  • @Magister
    link
    516 hours ago

    Linux is C only, ever read the rant by Linus last century about C++ ? I was there, in usenet

        • Possibly linux
          link
          fedilink
          English
          115 minutes ago

          The problem is that both Rust and Go are huge. The compiled binaries are bigger and the compilers themselves and slower and more resource intensive. The current benefit to C is that is lean and compiles quickly.

    • Lucy :3
      link
      fedilink
      53 hours ago

      I’ll never touch Rust.

      I hate the syntax and cargo too much for that. If that means that I’ll never write mission critical, low level code, so be it.

        • Lucy :3
          link
          fedilink
          22 hours ago

          Well - I of course prefer a centralized package manager like pacman, which I also use for python packages etc., but I mainly dislike the building process of rust, which is usually done with cargo. No libraries, not even a global cache for already compiled dependencies, no distcc. This makes it infinitely slower than most C/C++ projects. Compiling the kernel is literally faster than compiling a “simple” project like spotify_cli (500+ dependencies, depending on configuration).

          So it’s ass from a user perspective, waiting for stuff to compile (just for it to fail, and start from scratch, as some stuff needs a clean build/src dir), and imo very weird from a dev perspective.

    • @TootSweet
      link
      English
      526 hours ago

      Right? It’s in the kernel and everything now. Linus likes it. Linus hates everything. HOW MUCH ARE THEY PAYING HIM?

      • Ephera
        link
        fedilink
        English
        85 hours ago

        Did he actually say that he likes it? My impression was that it’s not his comfort zone, but he recognizes that for the vast majority of young programmers, C is not their comfort zone. And so, if they don’t hop on this Rust train, the Linux kernel is going to look like a COBOL project in a not too distant future. It does not happen very often that a programming language capable of implementing kernels gains wide-spread adoption.

      • Ephera
        link
        fedilink
        English
        25 hours ago

        I know you’re joking, but uh, both of those are (largely) implemented in Rust…

    • @[email protected]
      link
      fedilink
      English
      135 hours ago

      the author of C++ said that C gives you many opportunities to shoot yourself in the leg. You have a much less chance for this to happen with C++, but when it does, you will blow your whole lower body off

      • @Valmond
        link
        25 hours ago

        Yeah C++ is a bazooka, C is like the death of 1000 paper cuts.

        The paper cuts are all poisonous and kills you anyway.

        • @[email protected]
          link
          fedilink
          English
          24 hours ago

          I haven’t used either, but compiled a lot of C source code and they compiled or could be adjusted easier even for someone who barely knows what printf, fopen, or #include are

          • Possibly linux
            link
            fedilink
            English
            149 minutes ago

            The thing with C is that you probaby won’t know you messed it up. It happens silently as memory gets corrupted.

            Modern compilers are much more advanced but you still can overwrite stuff in memory with other stuff

    • TimeSquirrel
      link
      fedilink
      286 hours ago

      Wat? Don’t you dare talk that way about my favorite multiple personality disorder clusterfuck of a language.

  • @devfuuu
    link
    36 hours ago

    Only the internet to keep telling us these lies 😭

  • @[email protected]
    link
    fedilink
    English
    1
    edit-2
    5 hours ago

    for command line apps bash, python, perl, ruby and similiar high level languages are more than enough. You can write some Kali Lincox the louder you are the less you hear network probe stuff with any of these, or even a storage optimizer (BleachBit is almost entirely written in Python, which is a very highly abstracted language implemented from C) Rust and C are only needed for performance-crtitical stuff (like rythm games) or/and directly interacting with hardware (drivers, firmware, system functions)

    • sepi
      link
      fedilink
      English
      24 hours ago

      Don’t listen to the newbie above. You can use whatever language you are comfy with that works for your situation.

      • @[email protected]
        link
        fedilink
        English
        44 hours ago

        i never said you can’t. But high level languages were made for high level programming, and low level for low level programming. If you only know C, sure, you can write a desktop music player, but it will be much harder than just using Java, or even Python, since both of these languages are known about their extensive prewritten libraries. And you have to write much less, which means less room for error. Using a high level language will also benefit you if you decide to port your app to a drasticly different operating system. You can use the same codebase for Python, and for Java too to seamlessly run the program on any other os supported by these languages. In C, you need to adjust a lot of things, i know from experience that Linux C source can compile and run on windows, but it is extremely rare and can introduce bugs. However, you are right that C is highly multifunctional. If you know it, you can write any low level software or desktop app. And it also runs mich faster than any high level intrepeted language. And even if i could be considered a beginner, i actually study software development and testing, so i have an idea what i’m talking about