• lobut@lemmy.ca
    13·
    5 hours ago

    Not a word of a lie, I saw a “segmentation fault” error in JavaScript.

    Can’t remember how we resolved it, but it did blow my mind.

    • palordrolap@fedia.io
      121·
      8 hours ago

      As at least one nautically themed childrens’ book surely has it: C is for crab.

      Coming at programming sideways feels more like a Haskell or Prolog thing, though.

      • milicent_bystandr@lemm.ee
        1·
        59 minutes ago

        Apple is for ADA

        Ball is for BASH

        Crab is for C

        Dog is for D

        Elephant is for Ecsmascript

        Fox is for F#

        Goat is for Go

        House is for Haskell

        Igloo is for

        …okay I got stuck there.

    • Rednax@lemmy.world
      7·
      10 hours ago

      I mean, at the end of the day, if you really understand your language of choice, you know that it is jusf a bunch of fancy libraries and compiler tricks of top of C. So in my mind, I’m a fully evolved programmer in a language, when I could write anything I can write in that language in C instead.

      • lime!@feddit.nuEnglish
        14·
        10 hours ago

        only true if your language compiles to c. fortran peeps are safe.

      • nialv7@lemmy.world
        5·
        8 hours ago

        It’s not what you can use that language to do - all general purpose languages are Turing Complete, so what you can do with them is exactly equal. It is about what the language will do for you. Rust compiler will stop you from writing memory unsafe code, C compiler cannot do that.

        • Rednax@lemmy.world
          41·
          8 hours ago

          But how does the Rust compiler do that? What does it actually check? Could I write a compiler in C that does this check on a piece of Rust code?

          C is so simplictic, that if I can write a piece of functionality in C, I must understand its inner workings fully. Not just how to use the feature, but how the feature works under the hood.

          It is often pointless to actually implement the feature in C, since the feature already has a good implementation (see the Rust compiler for the memory safety). But understanding these features, and being able to mentally think about what it takes in C to implement them, is still helpfull for gaining an understanding of the feature.

        • qjkxbmwvz@startrek.website
          3·
          8 hours ago

          …are Turing Complete, so what you can do with them is exactly equal.

          But they’re only equal in the Turing complete sense, which (iirc) says nothing about performance or timing.

    • sbv@sh.itjust.worksEnglish
      18·
      10 hours ago

      I feel like Rust would be some complaint from the compiler saying that some apparently unrelated struct can’t be Send/Sync for some inscrutable reason. Or something about pinning a future.

      • CEbbinghaus@lemmy.world
        411·
        12 hours ago

        I would disagree. Especially since unlike npm every part of cargo was through through with all the experience and knowledge gained from npm, pip, nuget & co.

        I have a LOT more problems with npm over cargo. Also it’s 1 tool and not 100 different tools to do the same job (npm, pnpm, yarn, bun, deno, etc…)

  • ulterno@programming.devEnglish
    24·
    12 hours ago

    C trying to take the shortest path to the goal.
    Would probably have won (and broken the universe), if the referee didn’t exist.

  • grue@lemmy.world
    16·
    12 hours ago

    This implies that Javascript will get moving in the correct direction once it finishes installing dependencies, but it’s just going to get fucked with incorrect behavior that doesn’t even have the courtesy to throw an actual error.

  • Redkey@programming.dev
    52·
    10 hours ago

    “NPM install” isn’t going to be the direct result of a race condition in JavaScript. And while I’m not familiar with Python, I’d guess that an “Indentation error” wouldn’t be one either. A missing library or syntax error that’s only discovered by executing a particular branch is still just a missing library or syntax error, not a race condition.

    Also, while Node.js is popular, it isn’t an integral part of JavaScript in the way that the other errors are integral to their respective languages.

    • lime!@feddit.nuEnglish
      13·
      9 hours ago

      none of these are race conditions, they’re just runtime errors. python only parses code when it is about to run that block so you can absolutely get a crash from bad indentation.

      in my experience, the js world’s focus on developer ergonomics has absolutely yielded some insane situations where running an installed script has caused it to start downloading more dependencies. however, this has unfortunately started happening in python too lately.