(joke in the title stolen from a redditor)

Context: some Rust kid vandalized cppreference.com today.

  • jasory
    link
    fedilink
    arrow-up
    12
    ·
    1 year ago

    Pretty sure syntax is the only one that is even related to what a language is. All the rest are just ecosystem development primarily effected by popularity.

    • TootSweet@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      And the ecosystem affects whether when I run into an obstacle, I can google for 5 minutes to find the solution or whether I’ll spend the next three days trying dozens of incorrect approaches suggested by StackOverflow answers and random comments on language-specific forums and Wordpress blog posts etc. Whether you consider “the ecosystem” part of the language or not, it’s worth considering when choosing a language to work in.

      • jasory
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        1 year ago

        Sure but, this isn’t about the actual language. For instance I like Ada, there isn’t a lot of public support for it and you’re mostly left with the RM and GNAT manuals. But none of this is relevant to Ada as a language. Which was really all I was saying, you should probably split complaints about the ecosystem and the actual language affecting viability.

        • TootSweet@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 year ago

          Of course it’s relevant to (my or anyone else’s use of) Ada as a language. And for any language the language and culture influence each other too much to consider them entirely separate. The attitude of the community invariably ends up being reflected in the syntax and standard library (and third party tools/libraries/documentation) of the language and vice versa. If you want in your head to decide there’s a distinction there, I guess that’s fine, but such a distinction has no practical benefit to a developer making the decision what language to use for such-and-such use-case.