Github language popularity by pull requests

https://madnight.github.io/githut/#/pull_requests/2024/1
How come Kotlin and Swift are behind Rust?

Can someone give me an honest and objective opinion on whether Rust is a meme? I keep being told by IQfy to ignore the language but it keeps creeping up in popularity.

Shopping Cart Returner Shirt $21.68

DMT Has Friends For Me Shirt $21.68

Shopping Cart Returner Shirt $21.68

  1. 2 weeks ago
    Anonymous

    The only thing you have to know is that C++ is eight times more popular than Rust even on writing new code on github.
    Not even talking about the total C and C++ dominance on whats installed on whatever device you are using right now.

    • 2 weeks ago
      Anonymous

      Yeah, because most of the "new code" on C and C++ is fixing memory bugs.

  2. 2 weeks ago
    Anonymous

    Rust is horribe but so is C++ poeple who like those languages are try-hard autists. There no reason to have that much syntactical complexity.

  3. 2 weeks ago
    Anonymous

    Why don’t we ever see homosexuals shilling Go nonstop when it’s a generally non controversial language that’s also memory safe?
    It’s because Go users are busy writing code while Rust users are busy arguing on social media, isn’t it

    • 2 weeks ago
      Anonymous

      >Why don’t we ever see homosexuals shilling Go nonstop
      you sure?

    • 2 weeks ago
      Anonymous

      GC languages are a dime a dozen nocode frogtard.

      • 2 weeks ago
        Anonymous

        >as if lacking garbage collection is a feature
        Why don’t you just say “languages with variables are a dime a dozen” or “languages with control flow statements are a dime a dozen”

        • 2 weeks ago
          Anonymous

          it is a feature, now frick off until you know the basics of computer science.

    • 2 weeks ago
      Anonymous

      it isn't memory safe. I don't know why go tards say this.
      you can literally data race an interface because fat pointer operations aren't atomic.

    • 2 weeks ago
      Anonymous

      >Why don’t we ever see homosexuals shilling Go nonstop
      We do tho?

  4. 2 weeks ago
    Anonymous

    JavaScript at #1 with 17.2%, kind of low given the number of npm modules

  5. 2 weeks ago
    Anonymous

    >Python
    Fricking casuals.

    • 2 weeks ago
      Anonymous

      >programming to get things done is… LE BAD

  6. 2 weeks ago
    Anonymous

    many Java and C++ are from undergrads using github for their group project

  7. 2 weeks ago
    Anonymous

    https://github.com/madnight/githut?tab=readme-ov-file#pull-requests
    Looks like it is based on the no.1 language of each repo, not individual PRs.
    Not a very good measurement, if you have multi-lang repo all PRs are attributed to the lang with the most percentage

  8. 2 weeks ago
    Anonymous

    Pythonchads, we won.
    >objective opinion on whether Rust is a meme
    It had muh safety autism and muh typing autism and horrible syntax, also it wants to be a system language so bad but it has no system, then there's no spec, etc, etc.

  9. 2 weeks ago
    Anonymous

    Memory bugs are very nasty. They're very difficult to debug because they can fly under the radar and then get triggered randomly which makes them almost impossible to reproduce them, and it gets even worse if you add multithreading, IPC, and networking into the mix.
    Rust is designed in such a way where such bugs are impossible, because when it detects a situation that could cause a memory bug, the compiler throws an error. The time you spend solving Rust's compiler errors is more than worth it for the time you save debugging segmentation faults or memory bugs. Other languages have a Garbage Collector running constantly on the background to get the same degree of safety, but that causes a performance hit. Rust doesn't need that so it's as safe as other "modern" languages, while being as fast as C and C++. Also the fact it borrows quite a lot of time-saving and line-saving features from other programming languages sweetens the deal even more.

    • 2 weeks ago
      Anonymous

      So what's the catch? Why is it such a controversial language?

      • 2 weeks ago
        Anonymous

        Most of the criticism is outdated. Rust is a relatively new language so up until recently it had quite a lot kinks to iron. Rust exploded in popularity when the most important ones got ironed out.
        Some still valid criticisms is that the borrow checker (the thing that checks for memory bugs) is quite strict and it's difficult to work with if you're new to Rust, and that the compilation is quite slower than other languages precisely because of those checks.
        IQfy related criticisms mostly boil down to >muh trannies for the /misc/tards or >muh simplicity for people who have only made toy projects in C and shit themselves when they see a "::" in a line of code.

        • 2 weeks ago
          Anonymous

          >Why is it such a controversial language?
          it isn't.

          Okay. So, coming from a python background, should I learn rust directly or spend some time with C and C++ first to be able to better appreciate what rust brings to the table?

          • 2 weeks ago
            Anonymous

            I don't know. why don't you stop asking moronic questions and actually do something? wtf is this shit? I swear this site really is full of morons and freshies.

            frick op, frick jannies and frick you.

          • 2 weeks ago
            Anonymous

            Start with C. It's quite simple for beginners (our uni's introductory course taught C), and a good introduction to the whole memory management thing with pointers and whatnot. Going straight to Rust is possible but more difficult.
            C++ is kind of a mess but learning some its newer more advanced features (C++11 or newer) will make transitioning to Rust more easy.

          • 2 weeks ago
            Anonymous

            Thanks.

          • 2 weeks ago
            Anonymous

            You don't need Rust, if you come from Python and want to understand low level just learn C and maybe some assembly of choice too, Python main implementation is written in C.

          • 1 week ago
            Anonymous

            Start with C. It's quite simple for beginners (our uni's introductory course taught C), and a good introduction to the whole memory management thing with pointers and whatnot. Going straight to Rust is possible but more difficult.
            C++ is kind of a mess but learning some its newer more advanced features (C++11 or newer) will make transitioning to Rust more easy.

            Why even use rust or cpp?
            use python and ffi to c.
            You dont even have to be that good at c.

          • 1 week ago
            Anonymous

            >ffi to c.
            lol. ever used numpy?
            c ffi is a pain in the ass.

          • 1 week ago
            Anonymous

            >You dont even have to be that good at c.
            yes you do. CPython will break your code eventually. Reminder GIL is going away so all your C shitcode is probably broken. A lot of people I know are literally being paid to fix up the global state infecting a lot of C code used in Python.

          • 1 week ago
            Anonymous

            >ffi to c.
            lol. ever used numpy?
            c ffi is a pain in the ass.

            >c ffi
            or just use Cython

      • 2 weeks ago
        Anonymous

        >Why is it such a controversial language?
        it isn't.

    • 2 weeks ago
      Anonymous

      >Rust is designed in such a way where such bugs are impossible
      AHAHAHA HAHAHAHAHAHAHA
      >Other languages have a Garbage Collector running constantly on the background to get the same degree of safety
      AAAAASHAHAHHAHAHAHAHAHAH

      • 2 weeks ago
        Anonymous

        This definitely looks like a valid rebuttal to what he said and not unhinged at all

        • 2 weeks ago
          Anonymous

          this is IQfy. enjoy your stay.
          jannies don't do shit and this is literally the worst board next to /misc/ and, obviously, /b/.

        • 2 weeks ago
          Anonymous

          >muh rebuttal
          there's nothing to say about what he said because it's top tier moronation. just laugh at skidz and move on.
          or are you one of those people who need a source and a peer reviewed study to proof the sky is blue?

          • 2 weeks ago
            Anonymous

            if you want to go that route though ever, the burden of proof is on the other guy, not me. but I won't wait it out, because you cannot back his statements up.

          • 2 weeks ago
            Anonymous

            if the sky is blue explain this

          • 2 weeks ago
            Anonymous

            simple, you're an obnoxious pedantic c**t

          • 2 weeks ago
            Anonymous

            imagine getting so btfo you have to continue making low quality garbage posts.
            you will never be a coder.

          • 1 week ago
            Anonymous

            btfo by what? by a moron purposely misunderstanding my analogy? don't think so. anyway, if your only retort is calling me a nocoder I will accept that you and xim/xer don't know what you're talking about.
            rustroons btfo forever tbh

      • 1 week ago
        Anonymous

        I don't see anything wrong with what he said.

        • 1 week ago
          Anonymous

          what mitigations are in place to stop the programmer from fricking up?
          how does GC prevent these frick ups?
          only use after free and leaks, yes. overflows, underflows, smashing, and more corruption and UB can happen in rust as well as GC languages, even without using unsafe.

          • 1 week ago
            Anonymous

            > overflows, underflows, smashing
            If you used Rust idiomatically, we use iterators to avoid direct access as much as possible. Also we have nth() that returns Option<T> which we can match on.
            This is prevents ootb errors in Rust.

            Most GC languages do not make idiomatic use of Option idx but they usually throw a ootb exception.

          • 1 week ago
            Anonymous

            >if you use XYZ idiomatically
            read
            >if you don't make mistakes, you won't have problems
            this shit is in """idiomatic""" C too, btw

          • 1 week ago
            Anonymous

            >oh no rust doesn't solve turing complete problems and doesn't believe in checking carry bits for every math operation
            >it's over
            literally use the language before commenting. if you actually know C++, you'd just know.

          • 1 week ago
            Anonymous

            The way Rust expresses error is through tagged unions, the way C expresses errors is return code.
            In C, checking return code is optional, in Rust ignoring return causes compiler warning and not explicitly unwrapping a result type is a compiler error.
            They are not the same.

          • 1 week ago
            Anonymous

            see

            it took 4 people to come up with 1 (one) example, that again, doesn't prevent shit other than complete fricking Black folk from doing moronic shit. at which point you're beyond help anyway.

            fricktard
            feels good to do shit at your own discretion, given you're not a brainlet. and again, the systems are in place in both languages.

          • 1 week ago
            Anonymous

            >the systems are in place in both languages.
            show me your statically checked, type safe tagged union in C, shitter. protip, you can't.

          • 1 week ago
            Anonymous

            >goalposts are not even in sight anymore

          • 1 week ago
            Anonymous

            Rust provides so many iterator methods for a good reason. It is indeed widely practiced to make use of iterators, we don't like making off0by one errors.

            Idiomatic rust code uses for x in ... {} syntax. Idiomatic C uses for int x = 0; x < something; x++ syntax.

            Don't strawman.

          • 1 week ago
            Anonymous

            the other advantage of rust iterators and rust as a whole is you can't trivially iterator invalidate without unsafe, unlike C++ where I see iterator invalidation at least every other 3 months.

          • 1 week ago
            Anonymous

            >what mitigations are in place to stop the programmer from fricking up?
            ultra strict aliasing rules enforced by mutable xor shared.
            really. you sound like a moron and you write posts like one too.
            go post low quality trash elsewhere.

          • 1 week ago
            Anonymous

            it took 4 people to come up with 1 (one) example, that again, doesn't prevent shit other than complete fricking Black folk from doing moronic shit. at which point you're beyond help anyway.

          • 1 week ago
            Anonymous

            >more low quality screeching
            you really have no clue what you're talking about.
            you can't "smash the stack" in Rust without unsafe and pointer twiddling
            Rust, unlike your shitlang has had checked_add, etc, for longer than you.
            you're a fricking nocoder.

          • 1 week ago
            Anonymous

            Jamie, pull up the GitHub repo with 20 exploits in ~~*safe*~~ rust.
            >WAAAAH NOCODER
            ahaha okay, I'll come back when your cult has written anything

          • 1 week ago
            Anonymous

            jannies. do us a fricking favor.
            I'm sick of this shit board. retreading the same non-technical arguments ad-nauseam, ai slop, it's over doomer posting.
            This is not IQfy - Technology, it's IQfy - Madhouse.

          • 1 week ago
            Anonymous

            >cries for jannies when people are immune to shilling
            good, now stop being a homosexual and post actual tech related shit.

            Rust provides so many iterator methods for a good reason. It is indeed widely practiced to make use of iterators, we don't like making off0by one errors.

            Idiomatic rust code uses for x in ... {} syntax. Idiomatic C uses for int x = 0; x < something; x++ syntax.

            Don't strawman.

            the other advantage of rust iterators and rust as a whole is you can't trivially iterator invalidate without unsafe, unlike C++ where I see iterator invalidation at least every other 3 months.

            >this one thing that's dead easy and has been the same for forever le bad
            at this point it's ergonomics and a filter for people who don't understand code.

          • 1 week ago
            Anonymous

            >good, now stop being a homosexual and post actual tech related shit.
            you first.
            all your posts have been unsubstantiated screeching.

          • 1 week ago
            Anonymous

            >overflows, underflows, smashing, and more corruption and UB can happen in rust as well as GC languages, even without using unsafe.
            Don't bounds checks solve this? In Rust as well as in typical GC languages you need to really go out of your way to disable those. (In Rust you need to replace arr[i] by unsafe { arr.get_unchecked(i) }.)

  10. 2 weeks ago
    Anonymous

    >How come Kotlin and Swift are behind Rust?
    Proprietary stats by MS, which has a vested interest in pushing their own languages.

    The whole statistic is made up and you cannot fact check it.

    • 1 week ago
      Anonymous

      >Proprietary stats by MS
      homie, this page is not made by MS, it's made with a thrid party github crawler.

  11. 2 weeks ago
    Anonymous

    >ToyScript
    >6th most popular language
    pfhahahaha suuure

  12. 2 weeks ago
    Anonymous

    >caring what other people do
    shant be me.

    • 2 weeks ago
      Anonymous

      You will post your favorite language
      You will partecipate in the flame war
      And you will be happy

  13. 2 weeks ago
    Anonymous

    1. Python: 17%
    2. JS/TS: 17%
    3. C/C++: 14%

  14. 2 weeks ago
    Anonymous

    Wow, spacies language is #1? That's whack. Proves everyone has ADHD now.

  15. 2 weeks ago
    Anonymous

    Who still develops Java in this day and age? Is it all jeets? Or are there big projects I just don't know about?

    • 2 weeks ago
      Anonymous

      Go and Java is all corpos.

    • 2 weeks ago
      Anonymous

      everyone? if you aren't a C# cuckold, you're a java jeet. Most software is just moving memory around and building shitty reports for morons.

  16. 2 weeks ago
    Anonymous

    Rust has less market share than Linux on the desktop lmao

    • 1 week ago
      Anonymous

      How can a free and open source programming language/operating system have a market share?

  17. 2 weeks ago
    Anonymous

    B-but IQfy told me Java is dead!! HOW IS THIS POSSIBLE!?!?

  18. 1 week ago
    Anonymous

    Pretty sure Kotlin and Rust popularity is making more people rediscover C, C++, and Java.

  19. 1 week ago
    Anonymous

    they are stupid zoomer languages

    once again java shows how it's done.

  20. 1 week ago
    Anonymous

    >java #2
    Good morning, we're almost there sirs.

Your email address will not be published. Required fields are marked *