• Knusper@feddit.de
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    Ah, right, my interpretation is that as long as you don’t need to touch the source code, you’re good.

    But yeah, it’s certainly not as clear cut. My pick would actually be Rust, because you can use it for pretty much everything, including web frontends via WebAssembly.
    However, in that case, you still write HTML+CSS, which technically may or may not be programming languages, and the DOM API is actually only documented in JavaScript. So, I wouldn’t need to write JS, but would still want to read it…

    • CameronDev@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      Thats probably the best way to look at it, otherwise it gets very difficult very fast.

      If markup languages are locked out, then rust has other problems, because you then can’t change your cargo.toml file anymore.

      And then there is the build script problem :/

      As a thought excercise this has been interesting, there certainly are a lot of inter-dependencies between languages the deeper you look.

      • Knusper@feddit.de
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Yeah, I found it quite interesting, too. To some degree, I’ve been wondering why it’s so natural for programmers to be programming language polyglots, even if they’re not actively nerds/excited about them.
        And yeah, this discussion made me realize that you basically can’t take a single step in programming without being confronted with multiple languages/syntaxes at once.