• katy ✨@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    3
    arrow-down
    13
    ·
    3 months ago

    i did valign years ago. /s

    also i think more needs to be said about a push to localise css (and html, really). the fact that it still requires programmers to be versed in english is pretty sad.

    • GetOffMyLan@programming.dev
      link
      fedilink
      arrow-up
      14
      ·
      3 months ago

      English is the most spoken language outside of its home country and it uses the simplest alphabet.

      It is a pretty sane choice.

      You could write yourself a nice preprocessor

      • addie
        link
        fedilink
        arrow-up
        6
        ·
        3 months ago

        It’s a simple alphabet for computing because most of the early developers of computing developed using it and therefore it’s supported everywhere. If the Vikings had developed early computers then we could use the 24 futhark runes, wouldn’t have upper and lower case to worry about, and you wouldn’t need to render curves in fonts because it’s all straight lines.

        But yeah, agreed. Very widely spoken. But don’t translate programming languages automatically; VBA does that for keywords and it’s an utter nightmare.

        • DaPorkchop_@lemmy.ml
          link
          fedilink
          arrow-up
          3
          ·
          3 months ago

          Or worse, Excel, which translates the function names but doesn’t do it automatically, so you can only open a spreadsheet if your Excel is configured to the same language as the spreadsheet was created in.

    • Kissaki@programming.dev
      link
      fedilink
      English
      arrow-up
      8
      ·
      3 months ago

      English source code is a universal language.

      I’ve never seen a need for localization beyond domain terminology. And I think it would be a huge detrimental.

      To implement it would be unnecessary significant complexity. Effort better spent elsewhere. And for programmers it’d be confusing. Think code snippets, mixing content, and the need for reserved word expansion or exclusive parsing scopes that would be even more complex and confusing.