• count_dongulus@lemmy.world
    link
    fedilink
    arrow-up
    45
    ·
    16 hours ago

    This is why I will never touch Javascript again. Long ago when I worked on web stuff, half my workflow was spent in the debugger tracing garbage to find where a typo was. The industry moved to Typescript, and now assuming the strictness checks are enabled, if some Typescript transpiles successfully, I can be 95% sure whatever fuckup I observe at runtime is a logic problem.

    Weakly typed languages were an awful idea. But in general, if the compiler isn’t able to detect most runtime issues (like with C++ here), it’s not going to be the most productive language to use for building solutions compared to smarter alternatives.

      • count_dongulus@lemmy.world
        link
        fedilink
        arrow-up
        11
        arrow-down
        1
        ·
        14 hours ago

        Try porting a very small bit of behavior into a new tiny library or module that is Typescript based and independently published. Enable the strictness checks in tsconfig - really, really resist the urge to use any, and enforce that any is disallowed in tsconfig. Familiarize yourself with its utility types that really trip new authors up. “Record” comes to mind here, and others that involve generics if you haven’t before worked with generics. Some of the type error messaging can be pretty obtuse - don’t be afraid to paste them into an LLM (or use Copilot enhanced Intellisense) to explain what it actually means. IMO the type violation messaging is a weak dev experience point for new authors, so don’t sweat it if you occasionally “struggle to make the squiggles go away”.

  • I Cast Fist@programming.dev
    link
    fedilink
    arrow-up
    20
    ·
    14 hours ago

    What surprised me the most was the speed of the compilation, must be a very small program. I tried to compile Godot from source once. Force-stopped it after 3 hours

    • Sylvartas@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      9
      ·
      13 hours ago

      How many cores do you have and what compiler was it ? Also RAM can help with huge codebases iirc. When I was working with UE5 I had the best Ryzen available with 128 Go of RAM, could compile the engine (which is much bigger than Godot) from source in less than 2 hours iirc (yes that is a full clean+rebuild, not just compiling recent changes)

    • Psythik@lemmy.world
      link
      fedilink
      arrow-up
      4
      arrow-down
      15
      ·
      14 hours ago

      Why are you trying to compile an actress? What is a human’s “source”? Their DNA? I’m surprised that the compiler even tried.

  • brucethemoose@lemmy.world
    link
    fedilink
    arrow-up
    95
    arrow-down
    1
    ·
    edit-2
    18 hours ago

    Meanwhile, Rust punches you in the face for the mere suggestion. Again. And again.

    Python happily nods, runs it one page at a time, very slowly, randomly handing things off to a C person standing to the side, then returns a long poem. You wanted a number.

    Assembly does no checking, and reality around you tears from an access violation.

    EDIT: Oh, and the CUDA/PyTorch person is holding a vacuum sucking money from your wallet, with a long hose running to Jensen Huang’s kitchen.

    • Jyek@sh.itjust.works
      link
      fedilink
      arrow-up
      9
      ·
      17 hours ago

      It makes sense to me. You start in the top left like how you read and then you get a direction for the order of the conversation. I read it naturally at intended the first time through.

  • henfredemars@infosec.pub
    link
    fedilink
    English
    arrow-up
    57
    ·
    19 hours ago

    Ah, C++. An endless supply of footguns where the difference between a junior and a senior dev is knowing what parts of the language to never use.

      • henfredemars@infosec.pub
        link
        fedilink
        English
        arrow-up
        11
        ·
        edit-2
        12 hours ago

        You can also make everything a smart pointer and be done with it.

        I can count on more than one hand the number of large scale projects where converting everything to smart pointers fixed major memory issues. Even if smart pointers can’t handle circular references, the number of projects that just don’t manage their memory correctly at all and were fixed by introducing these tools is way too high.

        • xmunk@sh.itjust.works
          link
          fedilink
          arrow-up
          3
          ·
          12 hours ago

          This is a bit embarrassing but the last time I actively worked in C++ it was with Qt and pre C++11.

          • henfredemars@infosec.pub
            link
            fedilink
            English
            arrow-up
            2
            ·
            11 hours ago

            Almost the same as me. All kinds of programming jobs. I usually end up working in Python or C, for embedded systems work.

            Of course, if you’re talking hobby, it could be anything.

        • CanadaPlus@lemmy.sdf.org
          link
          fedilink
          arrow-up
          2
          ·
          13 hours ago

          Which kind of smart pointer, with which kind of footgun? I mean, it’s better than not even trying I guess, but if it was actually a full solution you’d just have Rust.

          • henfredemars@infosec.pub
            link
            fedilink
            English
            arrow-up
            6
            ·
            12 hours ago

            You’re right. It’s a stop gap, but when you’re talking about a code base that has been maintained for 20 years plus you can’t really sell re-implementation.

            Most recently it was with an older version of C++ using shared pointers.

  • abcd@feddit.org
    link
    fedilink
    English
    arrow-up
    23
    ·
    17 hours ago

    Is C++ the first enemy that managed to win against one punch man?

  • Lemmist@lemm.ee
    link
    fedilink
    arrow-up
    50
    arrow-down
    7
    ·
    21 hours ago

    So? Do you really expect the compiler to UNDERSTAND the code?

    Here is a grammatically correct phrase for you to think:

    Compilers don’t paint tangential apostrophes unless the storm value is deeper than radish. Fraggles love radish.

    • Thinker@lemmy.world
      link
      fedilink
      arrow-up
      19
      ·
      17 hours ago

      Congratulations, you’ve illustrated the difference between syntax and semantics. But any competent compiler also handles semantics (just in a separate phase of compilation), because that’s necessary for any useful conversion to machine code, not to mention optimizations.

      • CanadaPlus@lemmy.sdf.org
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        13 hours ago

        It’s more like they handle a smaller, toy version of semantics that you can actually code a compiler for. In OP, something semantically correct in that version but not by common sense was accidentally written.

        Maybe an early LLM that talks about picking up fire would be a better analogy.

      • CanadaPlus@lemmy.sdf.org
        link
        fedilink
        arrow-up
        7
        ·
        13 hours ago

        C/C++ is mildly obsolete now, basically. Breaking the memory model is not really a small defect that’s a matter of taste.

      • kiri@ani.socialOP
        link
        fedilink
        arrow-up
        6
        arrow-down
        1
        ·
        19 hours ago

        There are C++ analyzers like this which are also designed to prevent it (if you have no choice between languages).

        • CanadaPlus@lemmy.sdf.org
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          13 hours ago

          I’ve seen things like this posted several times on here. It always turns out it doesn’t actually catch all the possible problems, or it’s garbage collected, or it’s non-usable for real code.

          If it was that easy, the people who wrote Rust with all it’s complexity and divergence from the norm were idiots, and I really don’t think they were.

          • kiri@ani.socialOP
            link
            fedilink
            arrow-up
            6
            ·
            13 hours ago

            It’s pleasure for me to write in rust, I really like how fast I can deploy a working solution (including debug time). As I mentioned, there are situations when, for some reason, you cannot do without C++. But you are right cpp-analyzers do not solve all possible problems.

      • Lemmist@lemm.ee
        link
        fedilink
        arrow-up
        8
        arrow-down
        21
        ·
        20 hours ago

        Prevent what? UNDERSTANDING the code?

        Yeah, Rust is quite successful in that :)

          • Lemmist@lemm.ee
            link
            fedilink
            arrow-up
            4
            arrow-down
            13
            ·
            19 hours ago

            That’s a rather old joke. Modern compilers print more adequate things on STL/templates related things.

            And it doesn’t make Rust any better.

            • kiri@ani.socialOP
              link
              fedilink
              arrow-up
              7
              ·
              18 hours ago

              Yeah, I know, that all just a humour. I almost always use C++, inspite of knowing rust (cz no jun vacncies for rust, but still). There is no modern language which is absolutely better than other one — compromises are everywhere, that’s why it’s a silly topic to argue about.

        • bitcrafter@programming.dev
          link
          fedilink
          arrow-up
          6
          arrow-down
          1
          ·
          15 hours ago

          You do not come across as clever as you think that you are when your central point is that you personally are not capable of understanding code written in a different programming language.

        • CanadaPlus@lemmy.sdf.org
          link
          fedilink
          arrow-up
          1
          ·
          13 hours ago

          I feel like a really bad job has been done of making it simple, honestly. Or at least was last I checked.

          Pointers allow aliasing XOR mutability. There’s all kinds of nuance layered on top of that if you look in the compiler developers resources, but that’s just to allow for all the different kinds of sugar people want in a modern language.

        • AngryCommieKender@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          19 hours ago

          I kinda want to look up Fraggle Rock to see what that show was about, but I’m worried I’ll be disappointed in my former self’s taste. I know I watched it when I was like 4-6 y/o.

          • Lemmist@lemm.ee
            link
            fedilink
            arrow-up
            5
            ·
            19 hours ago

            I watched it when I was 30 as a method of learning English. It wasn’t too childish.

  • Thorry84@feddit.nl
    link
    fedilink
    arrow-up
    33
    ·
    20 hours ago

    Typescript on the other hand: Exwuse me sir, you seem to have a little oopsie right here. Oh right! Let me just fix that right up.

    HERE ARE TWO THOUSAND ERRORS! YOUR PUNY LITTLE BUFFER CAN’T EVEN SCROLL BACK TO READ THEM ALL! AND YOU CALL YOURSELF A PROGRAMMER?

  • heavy@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    12
    ·
    19 hours ago

    I mean, the comic is fine I guess, but if it implies the Cpp lady is hitting you, it’s not. That would be the kernel, the lady did what you told her to do.